[
https://issues.apache.org/jira/browse/SLING-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740438#comment-14740438
]
Konrad Windszus commented on SLING-5015:
----------------------------------------
This is actually not true. I was experiencing another case which I describe in
SLING-5016.
The unregistration and registration of the different types of
SlingWebConsoleSecurityProviders work fine.
> 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)
