[
https://issues.apache.org/jira/browse/CXF-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Johansen updated CXF-6233:
---------------------------------
Description:
The RST call from STS client (STSClient.requestSecurityToken(...)) only sends
the AppliesTo element first time the call is done. On subsequent calls it is
omitted.
Apparently this happens because the IssuedTokenInterceptorProvider sets the
STSClient's addressingNamespace field to null in a finally block of the
issueToken(...) method
(org.apache.cxf.ws.security.policy.interceptors.IssuedTokenInterceptorProvider
line 544). The STSClient requires this field to be non-null to set the element.
A workaround is to enable the «addressing» feature on the CXF bus. This makes
sure that an AddressingProperties is available on the message context, whic STS
client uses as an alternative way to get the addressingNamespace property:
{noformat}
<cxf:bus>
<cxf:features>
<wsa:addressing allowDuplicates="false"
xmlns:wsa="http://cxf.apache.org/ws/addressing"/>
</cxf:features>
</cxf:bus>
{noformat}
was:
The RST call from STS client (STSClient.requestSecurityToken(...)) only sends
the AppliesTo element first time the call is done. On subsequent calls it is
omitted.
Apparently this happens because the IssuedTokenInterceptorProvider sets the
STSClient's addressingNamespace field to null in a finally block of the
issueToken(...) method
(org.apache.cxf.ws.security.policy.interceptors.IssuedTokenInterceptorProvider
line 544). The STSClient requires this field to be non-null to set the element.
Priority: Minor (was: Major)
> STS client only sends AppliesTo on first RST call
> -------------------------------------------------
>
> Key: CXF-6233
> URL: https://issues.apache.org/jira/browse/CXF-6233
> Project: CXF
> Issue Type: Bug
> Components: STS
> Affects Versions: 3.0.3
> Reporter: Thomas Johansen
> Priority: Minor
>
> The RST call from STS client (STSClient.requestSecurityToken(...)) only sends
> the AppliesTo element first time the call is done. On subsequent calls it is
> omitted.
> Apparently this happens because the IssuedTokenInterceptorProvider sets the
> STSClient's addressingNamespace field to null in a finally block of the
> issueToken(...) method
> (org.apache.cxf.ws.security.policy.interceptors.IssuedTokenInterceptorProvider
> line 544). The STSClient requires this field to be non-null to set the
> element.
> A workaround is to enable the «addressing» feature on the CXF bus. This makes
> sure that an AddressingProperties is available on the message context, whic
> STS client uses as an alternative way to get the addressingNamespace property:
> {noformat}
> <cxf:bus>
> <cxf:features>
> <wsa:addressing allowDuplicates="false"
> xmlns:wsa="http://cxf.apache.org/ws/addressing"/>
> </cxf:features>
> </cxf:bus>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
