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

ASF subversion and git services commented on DISPATCH-200:
----------------------------------------------------------

Commit aea968659fc4d519ee4b9fa4417db0bdd0e770f8 in qpid-dispatch's branch 
refs/heads/master from [~ganeshmurthy]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=aea9686 ]

DISPATCH-200 - Add back call to qd_connection_set_user(qd_conn) which was 
accidentally removed during previous checkin


> Flexible mapping from x.509 certificates to an identity
> -------------------------------------------------------
>
>                 Key: DISPATCH-200
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-200
>             Project: Qpid Dispatch
>          Issue Type: New Feature
>          Components: Container
>            Reporter: Ted Ross
>            Assignee: Ganesh Murthy
>             Fix For: 0.6
>
>
> x.509 certificates contain structured data.  It is necessary to be able to 
> generate a unique identity from a certificate for the purpose of indexing 
> into access policy.
> The proposed feature will contain a descriptor that is part of an ssl-profile 
> configuration that specifies the format and content of the identity in terms 
> of the fields of a certificate.
> For example, the identity can be the certificate fingerprint, or the 
> distinguished name, or the combination of more than one field.
> A further enhancement is to provide a secondary mapping from the above 
> identity to a configured nickname.  For example, a user may want to use the 
> fingerprint as the identity field but wishes to write policy and view 
> management data containing a more friendly "display" name rather than the raw 
> fingerprint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to