[
https://issues.apache.org/jira/browse/CXF-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085158#comment-14085158
]
Christian Schneider commented on CXF-5118:
------------------------------------------
Hi Piotr,
please do not take Sergeys -100 coment personal. I think he is just
disappointed that you did not change your patch according to his comments. If
you want your changes to be included in CXF you will have to actively work with
the existing committers and PMC members (or more precisely the ones that take
part in the discussion.. namely Sergey and me). At Apache the way to solve a
conflict in opposing ideas in design is to ideally find a solution that
everyone is happy with. So while it makes sense to discuss opposing ideas for
some time we then have to settle down on a solution we can all agree with. I am
also notorious for discussion heatedly and trying to push my idea if I think it
is the right solution. This often leads to frustration though as others with a
different opinion have to draw their point then again and again which costs a
lot of time and effort.
So if you are still interested to work with us which I hope then we have to
find some common ground to get to a solution we all agree with.
What I will do now is to also create a clone on github and show a minimal
solution that can solve the actual problem we try to solve using minimal
changes in code. I hope we can agree on this as a starting point. I will then
open a new issue where I show my proposal for the CallbackHandlerProvider. We
can then discuss on this separately from the cert problem.
[~sergeyb] I did not fully understand what your solution would look like. I
hope it is very similar to the minimal solution I will show. If not then I
think it would also make sense if you could show your solution in a clone too.
Christian
> 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)
