You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Alessio Soldano (JIRA)" <ji...@apache.org> on 2012/05/10 13:11:53 UTC
[jira] [Created] (CXF-4304) Complete WSA support for STS client
configuration via EPR
Alessio Soldano created CXF-4304:
------------------------------------
Summary: Complete WSA support for STS client configuration via EPR
Key: CXF-4304
URL: https://issues.apache.org/jira/browse/CXF-4304
Project: CXF
Issue Type: Improvement
Components: WS-* Components
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: 2.6.1, 2.5.4
The STS client can be configured using EPR provided into {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}Issuer element in an endpoint policy.
Currently, EPR Address is only parsed, then WS-MEX is used to try getting the STS wsdl contract and configure the client.
Regardless of the WS-MEX support (the EPR might not come with {http://schemas.xmlsoap.org/ws/2004/09/mex}MetadataSection), we should complete the EPR parsing to be able to read the whole EPR info that can be provided.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4304) Complete WSA support for STS client
configuration via EPR
Posted by "Alessio Soldano (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessio Soldano resolved CXF-4304.
----------------------------------
Resolution: Fixed
> Complete WSA support for STS client configuration via EPR
> ---------------------------------------------------------
>
> Key: CXF-4304
> URL: https://issues.apache.org/jira/browse/CXF-4304
> Project: CXF
> Issue Type: Improvement
> Components: WS-* Components
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: 2.6.1, 2.5.4
>
>
> The STS client can be configured using EPR provided into {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}Issuer element in an endpoint policy.
> Currently, EPR Address is only parsed, then WS-MEX is used to try getting the STS wsdl contract and configure the client.
> Regardless of the WS-MEX support (the EPR might not come with {http://schemas.xmlsoap.org/ws/2004/09/mex}MetadataSection), we should complete the EPR parsing to be able to read the whole EPR info that can be provided.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4304) Complete WSA support for STS client
configuration via EPR
Posted by "Glen Mazza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272271#comment-13272271 ]
Glen Mazza commented on CXF-4304:
---------------------------------
Background on endpoint reference (EPR): http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/#eprs
> Complete WSA support for STS client configuration via EPR
> ---------------------------------------------------------
>
> Key: CXF-4304
> URL: https://issues.apache.org/jira/browse/CXF-4304
> Project: CXF
> Issue Type: Improvement
> Components: WS-* Components
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: 2.6.1, 2.5.4
>
>
> The STS client can be configured using EPR provided into {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}Issuer element in an endpoint policy.
> Currently, EPR Address is only parsed, then WS-MEX is used to try getting the STS wsdl contract and configure the client.
> Regardless of the WS-MEX support (the EPR might not come with {http://schemas.xmlsoap.org/ws/2004/09/mex}MetadataSection), we should complete the EPR parsing to be able to read the whole EPR info that can be provided.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira