[
https://issues.apache.org/jira/browse/CXF-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14092189#comment-14092189
]
Piotr Klimczak commented on CXF-5118:
-------------------------------------
I have one with CXF 2.7.x, but unfortunately starting from tomorrow i will be
working on customer site so will have very limited access/time. So I cannot
give a guarantee i will find time for this tomorrow or even in few next days.
But before I try, just wondering how CXF would behave at all with two same
class interceptors?
How about traceability and interceptor chain order management? How can we have
a guarantee that 1st will be executer before 2nd?
Please note that in CXF order (before, after) is determined by class names OR
unique object hashes (if explicitly set). So if we use 2 same interceptors (if
it is allowed at all) in same chain it means we cannot fully manage their
order. There is an option to use unique IDs instead of class names, but it
really increases configuration complexity.
Those are my thoughts about above example.
BTW. Being learned by GNU Hurd project, i know we should not wait for perfect
solution as there is no such. So I am not trying to promote my solution by this
post. Just sharing my thoughts as requested to let Christian's solution to be
better.
Greetings
Piotr Klimczak
> 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)
