Details

    • Type: Bug
    • Status: Coding In Progress (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1.9.2.CR1
    • Component/s: HTTP
    • Labels:
      None

      Description

      Presently the logout handler is just a Runnable, the problem with this is if it needs any state it means a lambda or an instance of a class tends to be needed to hold the state e.g.

          private void setupProgramaticLogout(HttpScope sessionScope) {
              logoutHandlerConsumer.accept(() -> {
                  sessionScope.setAttachment(AUTHENTICATED_IDENTITY_KEY, null);
              });
          }
      

      It would likely be better for the logout handler to be able to request the scope it needs so maybe pass in the 'org.wildfly.security.http.HttpServerScopes' at the very least.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                aabdelsa Ashley Abdel-Sayed
                Reporter:
                dlofthouse Darran Lofthouse
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: