[
https://issues.apache.org/jira/browse/KNOX-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117661#comment-15117661
]
ASF subversion and git services commented on KNOX-655:
------------------------------------------------------
Commit 62c759678df9852e92b0f54edd6ed8d2a99cf6ea in knox's branch
refs/heads/master from [~lmccay]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=62c7596 ]
KNOX-655 - Pac4j Provider Client Selection from client_name Query Parameter
(Jérôme Leleu via lmccay)
> Pac4j Provider Client Selection from client_name Query Parameter
> ----------------------------------------------------------------
>
> Key: KNOX-655
> URL: https://issues.apache.org/jira/browse/KNOX-655
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Larry McCay
> Assignee: Jérôme Leleu
> Fix For: 0.8.0
>
> Attachments: KNOX-655-002.patch, knox655.patch
>
>
> From dev@ list:
> "In pac4j, we have a callback controller which uses the client_name
> parameter to finish the login process and a protection filter which
> protects a resource and redirects the user to the identity provider for
> login. Since pac4j 1.8, most libraries using it now accept a client_name
> parameter in the protection filter as well to choose the authentication
> mechanism to use if the user is not authenticated.
> With Knox, this feature (choosing the authentication mechanism with the
> client_name parameter) is not available as this parameter is already used
> to define if it's a callback or an access. This could be changed and we
> could opt for a new convention, like a new pac4jCallback parameter to say
> if it's a callback or not. And this way, you could choose on the fly which
> authentication mechanism you want to use."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
