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

Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/09/28 23:29:00 UTC

[jira] [Commented] (KNOX-1072) Add Client Cert Required Capability to KnoxToken

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

ASF subversion and git services commented on KNOX-1072:
-------------------------------------------------------

Commit 7b4755d57c8998d1aed62c100124b8a94a3427db in knox's branch refs/heads/master from [~lmccay]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=7b4755d ]

KNOX-1072 - Add Client Cert Required Capability to KnoxToken

> Add Client Cert Required Capability to KnoxToken
> ------------------------------------------------
>
>                 Key: KNOX-1072
>                 URL: https://issues.apache.org/jira/browse/KNOX-1072
>             Project: Apache Knox
>          Issue Type: Bug
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>
> Token exchange is becoming a popular feature from Knox authentication services. Currently there is no way to establish and enforce the identities that are trusted to request a token for another given token or set of credentials.
> This change allows for a configured list of allowed principals to be validated against the SubjectDN of the client presented X509Certificate.
> By coupling this with KNOX-1051, we are able to have an authenticated channel over which a token may be acquired along with authorization checks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)