Uploaded image for project: 'Keycloak'
  1. Keycloak
  2. KEYCLOAK-10700

Non blocking KeycloakInstalled loginDesktop() and logout()

    Details

    • Type: Feature Request
    • Status: Pull Request Sent (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 6.0.1
    • Fix Version/s: Backlog
    • Component/s: None
    • Labels:
      None
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      Currently there are only blocking variants of loginDesktop() and logout() at KeycloakInstalled.
      It means that if the methods are called they open an URL in browser and wait until they get callback from the Keycloak server.

      It makes not advisable to call them from the UI thread because they block it.

      But even if the methods are called from a worker thread so that the application is not blocked, they always open a server socket and start threads and there is no way to close the socket and to kill the associated callback threads from the application code.

      I would like to have non blocking versions which could return CompletableFuture<Void>. If the user cancels the returned CompletableFuture, also the opened server socket should be closed.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dpolivaev Dimitry Polivaev
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: