[
https://issues.apache.org/jira/browse/CXF-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089279#comment-14089279
]
Christian Schneider commented on CXF-5118:
------------------------------------------
Well spotted :-) I read in Tomcat JAASRealm that they alway use the first
principal as username. So I thought we might do the same. Do you think that
could work?
If not then we can call the callbackhandler to get the username if the handler
sets it. The problem with this approach is though that there might be cases
where the callbackhandler does not set a username so we can not generally rely
on that aproach. Currently we always set the username so for now it could work.
Which do you prefer?
About the Callbackhandlers for AuthorizationPolicy and UsernameToken. The
problem I see is that both may be present in the same call and they may differ.
So having two handlers allows the user to configure which he wants to use. If
at some point there is only UsernameToken or only AuthorizationPolicy in the
CXF code then we can delete one of the handlers or at least change the default
configuration. Technically we can of course combine both. I do not have strong
feelings against doing so. So if you prefer this way I will combine them.
> 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)
