[
https://issues.apache.org/jira/browse/CXF-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessio Soldano updated CXF-4308:
---------------------------------
Description:
Currently the STS client parses the contents of Issuer element in endpoint
contract to find out the address of STS.
The contract can actually include an EPR with address and *optionally* some
WS-MEX metadata the client could use to send a WS-MEX call to the STS.
If the MEX metadata are not available, the client can still send a WS-MEX call
to the address specified in the EPR WSA address, which could however result in
simply logging error messages (if the STS does not support WS-MEX, for
instance).
This jira is about offering an option for disabling such "aggressive" WS-MEX
invocation and avoiding using WS-MEX if the endpoint contract does not mention
the STS support that.
was:
Currently the STS client parses the contents of Issuer element in endpoint
contract to find out the address of STS.
The contract can actually include an EPR with address and -optionally- some
WS-MEX metadata the client could use to send a WS-MEX call to the STS.
If the MEX metadata are not available, the client can still send a WS-MEX call
to the address specified in the EPR WSA address, which could however result in
simply logging error messages (if the STS does not support WS-MEX, for
instance).
This jira is about offering an option for disabling such "aggressive" WS-MEX
invocation and avoiding using WS-MEX if the endpoint contract does not mention
the STS support that.
> Add option for disabling STS client WS-MEX invocation using WSA EPR address
> ---------------------------------------------------------------------------
>
> Key: CXF-4308
> URL: https://issues.apache.org/jira/browse/CXF-4308
> Project: CXF
> Issue Type: Improvement
> Components: WS-* Components
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: 2.6.1, 2.5.4
>
>
> Currently the STS client parses the contents of Issuer element in endpoint
> contract to find out the address of STS.
> The contract can actually include an EPR with address and *optionally* some
> WS-MEX metadata the client could use to send a WS-MEX call to the STS.
> If the MEX metadata are not available, the client can still send a WS-MEX
> call to the address specified in the EPR WSA address, which could however
> result in simply logging error messages (if the STS does not support WS-MEX,
> for instance).
> This jira is about offering an option for disabling such "aggressive" WS-MEX
> invocation and avoiding using WS-MEX if the endpoint contract does not
> mention the STS support that.
--
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
