cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-5118) Create CXF interceptor which will use HTTPS client certificates to create JAAS SecurityContext
Date Mon, 04 Aug 2014 09:48:13 GMT


Sergey Beryozkin commented on CXF-5118:

> Well the thing is to let the user decide.
> But I fully agree that primary reason of creating this solution is to provide password
less login.
I disagree, the solution should work with modules that can not be modified to accept the passwordless

> Using TLSUserToken gives additional layer of abstraction.
It does not to be honest, it add a new class holding a pair of properties, name + password,
and we have 2 such classes already
> Imagine if you have CertificateMapper returning TLSUserToken, you can create customized
version of it that will return some custom implementation of TLSUserToken (with password-
mapped or static or whatever) and then you could do whatever you want to later on with it.

I don't get it. Suppose it returns UsernameToken or AuthorizationPolicy. What blocks the custom
mapper not to set a password property or set if needed

> With default implementation it could have only user name. But it is important from my
point of view to leave the user some freedom here.

We still have to remember about users, who have to reuse their username/password functionality,
but they are ok for example to have same static password for all TECHNICAL accounts or equal
to some custom part of certificate.

Yes ! 

> Create CXF interceptor which will use HTTPS client certificates to create JAAS SecurityContext

> -----------------------------------------------------------------------------------------------
>                 Key: CXF-5118
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message