[
https://issues.apache.org/jira/browse/SLING-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424333#comment-15424333
]
Carsten Ziegeler commented on SLING-5868:
-----------------------------------------
[~anchela] Thanks for your contribution - I think it would make sense to split
the public API from the implementation as the impl is tied to Oak - that's not
bad by itself but if someone wants to provide a different implementation for
the API, it will depend on this bundle which depends on Oak.
Would it make sense to move the public API to auth.core?
> API to define and retrieve login path with along with authentication
> requirements
> ---------------------------------------------------------------------------------
>
> Key: SLING-5868
> URL: https://issues.apache.org/jira/browse/SLING-5868
> Project: Sling
> Issue Type: Sub-task
> Components: Authentication
> Reporter: angela
>
> When defining parts of the hierarchy that require authentication it would be
> handy to also be able to defined an optional, individual login path for that
> particular subtree.
> This functionality could additionally come with an API that would allow to
> identify the login path that corresponds to a given sling request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
