You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Andrei Shakirin (JIRA)" <ji...@apache.org> on 2013/11/24 11:13:36 UTC
[jira] [Updated] (WSS-485) Provide service endpoint as possible
X509 identifier in Crypto implementation
[ https://issues.apache.org/jira/browse/WSS-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Shakirin updated WSS-485:
--------------------------------
Attachment: crypto-endpoint.patch
Patch
> Provide service endpoint as possible X509 identifier in Crypto implementation
> -----------------------------------------------------------------------------
>
> Key: WSS-485
> URL: https://issues.apache.org/jira/browse/WSS-485
> Project: WSS4J
> Issue Type: New Feature
> Components: WSS4J Core
> Affects Versions: 2.0
> Reporter: Andrei Shakirin
> Assignee: Colm O hEigeartaigh
> Attachments: crypto-endpoint.patch
>
>
> In case of STS symmetric holder of key is useful to locate service certificates on the base of target service endpoint (WS-Trust AppliesTo). Service certificates can be located using XKMS in this case and it is not necessary that STS knows all service certificates. See conversation on CXF user list for details: http://cxf.547215.n5.nabble.com/CXF-WS-Trust-WS-SecureConversation-security-policy-questions-td5735026.html
> In order to implement this in CXF in correct way, I need some minor extension in WSS4J to introduce endpoint identification in Crypto and in WSConstants.
> Could you please review the patch and apply it?
> Regards,
> Andrei.
> Could you please review
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org