[
https://issues.apache.org/jira/browse/SLING-10248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-10248.
--------------------------------------
Resolution: Fixed
Refactored into an own service:
https://github.com/apache/sling-org-apache-sling-auth-core/commit/1b7c761e898617fb977b66144371308c58631252
decoupling the component from SlingAuthenticator
> Refactor: Move auth requirements handling into separate component
> -----------------------------------------------------------------
>
> Key: SLING-10248
> URL: https://issues.apache.org/jira/browse/SLING-10248
> Project: Sling
> Issue Type: Improvement
> Components: Authentication
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Auth Core 1.5.2
>
>
> The handling of auth requirements is currently split across three classes,
> the cache (path based holder), Sling Authenticator (for configuration) and
> SlingAuthenticatorServiceListener (service registrations)
> We should refactor this into a single class - to make the code cleaner but
> also easier testable
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
