[jira] [Commented] (SLING-5868) API to define and retrieve login path with along with authentication requirements
[
https://issues.apache.org/jira/browse/SLING-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426075#comment-15426075
]
angela commented on SLING-5868:
---
As discussed with [~cziegeler] the patch will be improved by
- moving the API to auth.core
- adjust {{SlingAuthenticator}} to make use of the optional
{{LoginPathProvider}}
> 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)
[jira] [Commented] (SLING-5868) API to define and retrieve login path with along with authentication requirements
[
https://issues.apache.org/jira/browse/SLING-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424468#comment-15424468
]
angela commented on SLING-5868:
---
we would use it at Adobe with a dedicated {{AuthenticationHandler}}
implementation that upon unsuccessful
{{AuthenticationHandler.requestCredentials}} tries to determine a login
resource and redirect the client instead of simply failing the authentication.
> 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)
[jira] [Commented] (SLING-5868) API to define and retrieve login path with along with authentication requirements
[ https://issues.apache.org/jira/browse/SLING-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424409#comment-15424409 ] Carsten Ziegeler commented on SLING-5868: - What would be a typical client of the new interface? > 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)
[jira] [Commented] (SLING-5868) API to define and retrieve login path with along with authentication requirements
[ https://issues.apache.org/jira/browse/SLING-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424404#comment-15424404 ] angela commented on SLING-5868: --- sure... if that makes sense for a broader Sling audience, I am more than happy to have the public API part in auth.core. in an initial step i just wanted to keep and discuss this new feature clearly separated from the other enhancements. > 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)
[jira] [Commented] (SLING-5868) API to define and retrieve login path with along with authentication requirements
[ https://issues.apache.org/jira/browse/SLING-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (SLING-5868) API to define and retrieve login path with along with authentication requirements
[ https://issues.apache.org/jira/browse/SLING-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424200#comment-15424200 ] angela commented on SLING-5868: --- [~cziegeler], I would appreciate if you could take a look at this contribution making use of the new API introduced with SLING-5792. Obviously it would be cool if that would make into the Sling contributions. > 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)
[jira] [Commented] (SLING-5868) API to define and retrieve login path with along with authentication requirements
[ https://issues.apache.org/jira/browse/SLING-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424197#comment-15424197 ] angela commented on SLING-5868: --- latest adjustment to final version of SLING-5792 at https://github.com/anchela/sling/commit/5cad189dda683f2b713009678636e9a1fde7 > 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)
[jira] [Commented] (SLING-5868) API to define and retrieve login path with along with authentication requirements
[ https://issues.apache.org/jira/browse/SLING-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384449#comment-15384449 ] angela commented on SLING-5868: --- see SLING-5792 for pull request > 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)
