You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2015/09/10 17:56:45 UTC

[jira] [Created] (SLING-5015) SlingWebConsoleSecurityProvider cannot deal with an unregistered SlingAuthenticator

Konrad Windszus created SLING-5015:
--------------------------------------

             Summary: SlingWebConsoleSecurityProvider cannot deal with an unregistered SlingAuthenticator
                 Key: SLING-5015
                 URL: https://issues.apache.org/jira/browse/SLING-5015
             Project: Sling
          Issue Type: Bug
          Components: Extensions
    Affects Versions: Web Console Security Provider 1.1.6
            Reporter: Konrad Windszus


Currently the {{WebConsoleSecurityProvider}} and {{WebConsoleSecurityProvider}} are only registered once manually during the startup phase. If afterwards the {{SlingAuthenticator}} is unregistered (e.g. because the {{JcrResourceResolverFactory}} has been reconfigured) the security providers will still stay active, although they are useless because they don't have any SlingAuthenticator they can use. Instead the security providers should be unregistered as well (that one is still able to use the webconsole at that time).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)