[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlrpc-dev
Subject:    [jira] [Closed] (WSS-485) Provide service endpoint as possible X509 identifier in Crypto implementat
From:       "Colm O hEigeartaigh (JIRA)" <jira () apache ! org>
Date:       2014-10-07 8:05:34
Message-ID: JIRA.12680921.1385287971000.206385.1412669134458 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/WSS-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Colm O hEigeartaigh closed WSS-485.
-----------------------------------

> 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.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.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]