[
https://issues.apache.org/jira/browse/SLING-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3193.
-------------------------------------
Resolution: Fixed
Implemented in rev 1534058.
I've also removed the dependency from SCR by handling component registration
and dependencies by hand.
> Implement WebConsoleSecurityProvider2 for integration with Sling Authenticator
> ------------------------------------------------------------------------------
>
> Key: SLING-3193
> URL: https://issues.apache.org/jira/browse/SLING-3193
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Extensions Web Console Security Provider 1.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Web Console Security Provider 1.0.2
>
>
> The current security provider implements only the WebConsoleSecurityProvider
> interface doing an auth based on username and password by trying to login
> into the repository. If the web console runs within the Sling context, we
> should rather use the Sling Authenticator for authentication. This would
> allow for a seamless integration without the need to retype a password while
> keeping the exact same checks
> We could enhance the module to register the type 2 interface if a Sling
> Authenticator is available, the old implementation if not for compatibility
--
This message was sent by Atlassian JIRA
(v6.1#6144)
