[
https://issues.apache.org/jira/browse/CXF-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085874#comment-14085874
]
Sergey Beryozkin commented on CXF-5118:
---------------------------------------
Piotr,
I was harsh yesterday with adding two zeroes to my -1, sorry it got you upset
(I've seen other people on other lists expressing their disagreement with -100
recently, it's kind of 'I really disagree' kind of thing which is 'sticky', and
I copied it here, but I'm not going to use it again any time soon). It was
really a plea to you to pause for a bit after I realized that we did not reach
the common consensus after seeing your last commit, after all the discussions.
Let me give a friendly advice and I do not mean it to be condescending: in our
line of work all of us have to be prepared to get our ideas rejected. I've been
facing such situations for a long time, even these days (not so much in CXF as
the team is more kind to me :-)), but in some other work I do. When I think
about some of the ideas I've had rejected I still feel upset about it. The
skill we all have to continuously master is to be able to get over it and stick
around and work toward the common solution which will likely be different to
what we expected. Exiting the process is not an option for me personally, even
though I do always consider it in such situations :-). So it is up to you. I
think you should continue.
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)
