You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2017/03/28 09:30:42 UTC

[jira] [Closed] (CXF-3203) Introduce CXF X509 token

     [ https://issues.apache.org/jira/browse/CXF-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh closed CXF-3203.
------------------------------------
    Resolution: Won't Fix

Closing this issue after consultation with Sergey - it only really makes sense to support X.509 certs with signatures.

> Introduce CXF X509 token 
> -------------------------
>
>                 Key: CXF-3203
>                 URL: https://issues.apache.org/jira/browse/CXF-3203
>             Project: CXF
>          Issue Type: Task
>          Components: Core
>            Reporter: Sergey Beryozkin
>
> CXF has its own UsernameToken which is used by AbstractUsernameTokenInterceptor sub-classes to populate the subject without dealing with WSS4J and making sure it works with policy-first cases along the line.
> Having CXF X509Token can make it straightforward for users to do the authentication and authorization in CXF with X509 certs and make it a common knowledge. Additionally a JAASLoginInterceptor should also be enhanced to handle X509 related callbacks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)