[
https://issues.apache.org/jira/browse/CXF-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089308#comment-14089308
]
Sergey Beryozkin edited comment on CXF-5118 at 8/7/14 3:07 PM:
---------------------------------------------------------------
Hi Christian, sure, lets have dedicated callback handlers.
re the name: before I added a constructor accepting a name,
DefaultSecurityContext did work exactly like that, i.e, it was assuming the
first Subject principal was a user. I think now it was to do with Subject doing
some re-ordering of the Principals. I'm afraid I do not remember the specific
case that led to it, but I'm sure it was added on request. This is as much as i
can add to it. So I think for the sake of keeping the existing application code
non-affected we should have a name hint. I think it is acceptable if we have a
case of a given handler not setting a name, nothing we can do about it, so your
proposed solution (call the handler to get the name) works.
Piotr, IMHO we should close down now on the Christian's code, it's a good start
IMHO, and then proceed from there and see what can be enhanced next or what
other alternatives can be provided (example, based on your code). People will
not have to use JAASLoginInterceptor if they don't want to...
Thanks, Sergey
was (Author: sergey_beryozkin):
Hi Christian, sure, lets have dedicated callback handlers.
re the name: before I added a constructor accepting a name,
DefaultSecurityContext did work exactly like that, i.e, it was assuming the
first Subject principal was a user. I think now it was to do with Subject doing
some re-ordering of the Principals. I'm afraid I do not remember the specific
case that led to it, but I'm sure it was added on request. This is as much as i
can add to it. So I think for the sake of keeping the existing application code
non-affected we should have a name hint.
Thanks, Sergey
> 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)
