[
https://issues.apache.org/jira/browse/CXF-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086149#comment-14086149
]
Sergey Beryozkin commented on CXF-5118:
---------------------------------------
Hi Christian
IMHO the code change you linked to is simple, IMHO it is quite perfect. It
reuses the code from Piotr to do with the default mapping, easy to
extend/override. This is as simple as it gets.
The only proposal: your version would only support a password-less logins. I
believe Piotr and myself agreed such logins might be somewhat controversial
though it may work in the constraint environments.
So please consider letting the mappers return the passwords too, I think the
solution should work for example with Tomcat LDap JAAS Module too; default
mapper would return a null passsword.
If you agree: I originally proposed returning AuthorizationPolicy or
UsernameToken. However lets indeed introduce a new class to make Piotr a bit
more happier :-), say TLSLoginToken. I'd propose TLSLoginToken simply extending
AuthorizationPolicy, so that in the future we'd be able to add few more mapping
properties which can help in the JAAS process.
Does it work for you ?
Thanks
> Create CXF interceptor which will use HTTPS client certificates to create
> JAAS SecurityContext
> -----------------------------------------------------------------------------------------------
>
> Key: CXF-5118
> URL: https://issues.apache.org/jira/browse/CXF-5118
> Project: CXF
> Issue Type: New Feature
> Components: Core
> Reporter: Sergey Beryozkin
> Assignee: Christian Schneider
>
> Use case:
> The user authenticates against the webservice using an X509 client
> certificate. In case of successful authentication the JAAS security context
> should be populated with a Subject that stores the user name and the roles of
> the user. This is necessary to support Authorization at a later stage.
> Design ideas
> The SSL transport will be configured to only accept certain client
> certificates. So we can assume that the interceptor does not have to do a
> real authentication. Instead it has to map from the subjectDN of the
> certificate to the user name and then lookup the roles of that user. Both
> then has to be stored in the subject's principles.
> The mapping could be done inside a JAASLoginModule or before. Inside will
> give the user more flexibility.
> The next step to retrieve the roles should be done in one of the standard
> JAASLoginModules as the source of the roles can be quite diverse. So for
> example the LdapLoginModule allows to retrieve the roles from Ldap. At the
> moment these modules require the password of the user though which is not
> available when doing a cert based auth.
> So I see two variants to retrieve the roles:
> 1. Change the loginmodules like the LDAP one to be configureable to use a
> fixed ldap user for the ldap connect and not require the user password. So
> the module would have two modes: a) normal authentication and group gathering
> b) use a fixed user to just retrieve roles for a given user
> 2. Store the user password somewhere (e.g. in the mapping file). In this case
> the existing LDAPLoginModule could be used but the user password would be
> openly in a text file
> 3. Create new LoginModules with the desired behaviour (fixed user and only
> lookup of roles)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
