Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Mon, 4 Aug 2014 09:58:13 +0000 (UTC)
From: "Piotr Klimczak (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12657234.1373538823026.5426.1407146293437@arcas>
In-Reply-To: <JIRA.12657234.1373538823026@arcas>
References: <JIRA.12657234.1373538823026@arcas>
Subject: [jira] [Comment Edited] (CXF-5118) Create CXF interceptor which
 will use HTTPS client certificates to create JAAS SecurityContext
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Piotr Klimczak edited comment on CXF-5118 at 8/4/14 9:57 AM:
-------------------------------------------------------------

In reference to TLSUserToken,
Well if we use UsernameToken or AuthenticationPolicy, we will not be able to do password less login with custom JAAS modules.
That is because JAASLoginModule requires to set both.
And I think that we should not change this logic for security reasons.
So when TLSUserToken is provided, then we can ignore the fact that there is no password, because it is up to JAAS module to handle this fact.
This is the only reason of using TLSUserToken- just avoiding amending current logic, on which many customers may be basing.


was (Author: nannou9):
In reference to TLSUserToken,
Well if we use UsernameToken or Authentication policy, we will not be able to do password less login with custom JAAS modules.
That is because JAASLoginModule requires to set both.
And I think that we should not change this logic for security reasons.
So when TLSUserToken is provided, then we can ignore the fact that there is no password, because it is up to JAAS module to handle this fact.
This is the only reason of using TLSUserToken- just avoiding amending current logic, on which many customers may be basing.

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