cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piotr Klimczak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-5118) Create CXF interceptor which will use HTTPS client certificates to create JAAS SecurityContext
Date Thu, 07 Aug 2014 15:32:12 GMT

    [ https://issues.apache.org/jira/browse/CXF-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089343#comment-14089343
] 

Piotr Klimczak commented on CXF-5118:
-------------------------------------

Which means you want to use 2 different Login Modules in parallel: LDAPLoginModule, customized
LDAPLoginModule.
As you can see we have 2 solutions on the tables.
The main difference between them that one is about to reuse JAASLoginInterceptor, second is
about to introduce new interceptor.

As I understand you "wantClientAuth" (which is optional).
If provided then handle it with your custom LDAPLoginModule.
If not provided then request for HTTP Authentications.

Your scenario will not work with the one that reuses JAASLoginInterceptor as it was designed
to work only with one Login Module.
Your scenario will work with TLSAuthenticationInterceptor only or altogether with JAASLoginInterceptor.

With TLSAuthenticationInterceptor altogether with unchanged JAASLoginInterceptor, all you
need is implement TLSSecuritySubjectProvider for example:
{code}
public class MySecuritySubjectProvider extends TLSSecuritySubjectProvider {
        private String contextName;

	@Override
	Subject getSubject(String userName, X509Certificate certificate) throws SecurityException
{
		CallbackHandler handler = new NamePasswordCallbackHandler(name, null); //password-less
		return login(contextName, handler);
	}
}
{code}

Done.
Your scenario is ready.
Once you provide HTTP Authentication data in request, then JAASLoginInterceptor will handle
it normally.


> 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)

Mime
View raw message