[
https://issues.apache.org/jira/browse/CXF-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084488#comment-14084488
]
Piotr Klimczak commented on CXF-5118:
-------------------------------------
Thanks Sergey for your answer.
Well yes- it is starting to be complex.
But I've done a step back in my thinking and for better understanding what I
mean you should do the same :).
TLS Authentication Handshake was not designed to work with JAAS and JAAS was
not designed to work with TLS Authenticated Handshake.
Those are two close but also completely different mechanisms. Especially
because message is already Authenticated. All we want to is rather to retrieve
roles from somewhere than doing another authentication.
So there is no real reason why to use both of those functionalities as a one
(in one iterceptor).
It is more like a workaround solution.
So maybe it is even bad idea to use JAAS for it at all?
I think that many users may want not to use JAAS (because of above problems)
but simply do custom implementation of some role retrieval functionality.
So this is the reason why in my opinion it should be separated interceptor to
JAAS one.
WDYT?
> 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)
