[
https://issues.apache.org/jira/browse/CXF-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086222#comment-14086222
]
Piotr Klimczak commented on CXF-5118:
-------------------------------------
A common scenerio for need to avoid JAAS authentication with TLS Authenticated
handshake is for example:
Let's say there is a BankX which have a web application used internally.
Assumptions:
1. In BankX each user has his own certificate- because it is secure!
2. This internal web app is doing REST calls from Javascript
3. There is an active directory (or open directory whatever) used to
authenticate users to their operating systems.
4. Users data is provided by directory service (roles, username and password).
So in this common scenario, you cannot:
1. Decrypt passwords from directory services (no matter if possible or not due
to security reasons)
2. Use technical password, because each user is using his own in time-
changeable password.
3. Do password-less login due to security reasons
So there is no way to authenticate this REST call with JAAS, meaning
JAASLoginInterceptor is not usable.
So in high sec scenarios, we NEED to avoid JAAS reauthentication at all.
If you are ok with fact that in high security scenarios JAASLoginInterceptor
will be unusable, then there is no problem.
> 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)
