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

Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2014/04/22 23:32:28 UTC

[jira] [Commented] (CXF-5705) OAuth2 Client should support public certificates in addition to client secret

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

Sergey Beryozkin commented on CXF-5705:
---------------------------------------

One possibility is to introduce ClientCredentials interface which can represent either a generated secret or public certificate however it may pose problems with persisting the Client model.

> OAuth2 Client should support public certificates in addition to client secret
> -----------------------------------------------------------------------------
>
>                 Key: CXF-5705
>                 URL: https://issues.apache.org/jira/browse/CXF-5705
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-RS, JAX-RS Security
>            Reporter: Sergey Beryozkin
>            Assignee: Sergey Beryozkin
>
> Right now Client can only have a secret which will be typically assigned to it during the client registration. Client should also support persisting public certificates of confidential clients.



--
This message was sent by Atlassian JIRA
(v6.2#6252)