[
https://issues.apache.org/jira/browse/RAMPART-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Buddhika resolved RAMPART-201.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Fixed as of r1074538.
Now the alias of the certificate can be accessed through the message context
property with the key "signatureCertAlias". (The corresponding constant is
RampartMessageData.SIGNATURE_CERT_ALIAS. )
> Add alias/certificate used for validating signature
> ---------------------------------------------------
>
> Key: RAMPART-201
> URL: https://issues.apache.org/jira/browse/RAMPART-201
> Project: Rampart
> Issue Type: Improvement
> Components: rampart-core
> Reporter: Bob Jacoby
> Assignee: Thilina Buddhika
> Priority: Minor
> Fix For: 1.6.0
>
>
> Set the alias (or certificate) Rampart used to verify the signature as a
> property in the message context.
> Reason:
> To allow other modules/handlers to know which certificate was associated with
> the signature. Rampart already performs this lookup within the keystore given
> the token reference within the security header. By including either the
> certificate or alias found during the lookup, subsequent code can use this
> information for various purposes (e.g. - retrieve externally stored
> properties based on the certificate used).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
