PM38681: JAX-RPC SignatureGenerator emits SAML 2.0 ValueType for a SAML 1.1 token in the SecurityTokenReference/KeyIdentifier element

Fixes are available

APAR status

Closed as program error.

Error description

JAX-RPC SignatureGenerator emits a SAML 2.0 value type for a
SAML 1.1 token in the SecurityTokenReference/KeyIdentifier
element.  The ValueType emitted is:

http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1
#SAMLID

It should be:

http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0
#SAMLAssertionID

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server users of   *
*                  WS-Security enabled JAX-RPC applications    *
*                  and custom SAML tokens                      *
****************************************************************
* PROBLEM DESCRIPTION: JAX-RPC SignatureGenerator emits SAML   *
*                      2.0 ValueType for a SAML 1.1 token in   *
*                      the                                     *
*                      SecurityTokenReference/KeyIdentifier    *
*                      element                                 *
****************************************************************
* RECOMMENDATION:  Install a fix pack that contains this APAR  *
****************************************************************
In the JAX-RPC WS-Security runtime, when a custom SAML token
is signed with STR-Transform, the ValueType that is emitted on
the KeyIdentifier in the SecurityTokenReference to the SAML
token is always a SAML 2.0 ValueType.  A SAML 1.1 token should
have a SAML 1.1 ValueType and a SAML 2.0 token should have a
SAML 2.0 ValueType:

SAML 1.1 ValueType:

http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0
#SAMLAssertionID

SAML 2.0 ValueType:

http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1
#SAMLID


Following is an example of the errant SecurityTokenReference
to a SAML 1.1 custom token:

<wss:SecurityTokenReference
xmlns:wss11="http://docs.oasis-open.org/wss/oasis-wss-wssecurity
-secext-1.1.xsd"
wss11:TokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-t
oken-profile-1.1#SAMLV1.1">
    <wss:KeyIdentifier
xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"
ValueType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-p
rofile-1.1#SAMLID">Assertion-uuidc1a1a525</wss:KeyIdentifier>
</wss:SecurityTokenReference>


Following is an example of what a SecurityTokenReference to a
SAML 1.1 custom token should look like:

<wss:SecurityTokenReference
xmlns:wss11="http://docs.oasis-open.org/wss/oasis-wss-wssecurity
-secext-1.1.xsd"
wss11:TokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-t
oken-profile-1.1#SAMLV1.1">
    <wss:KeyIdentifier
xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"
ValueType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-p
rofile-1.0#SAMLAssertionID">Assertion-uuidc1a1a525</wss:KeyIdent
ifier>
</wss:SecurityTokenReference>

Problem conclusion

The JAX-RPC WS-Security runtime is updated to emit the correct
ValueType on the SecurityTokenReference/KeyIdentifier element
for references to custom SAML 1.1 tokens.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.41, 7.0.0.19, and 8.0.0.1.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM38681
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-05-09
Closed date
2011-05-27
Last modified date
2011-05-27

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"610","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM38681: JAX-RPC SignatureGenerator emits SAML 2.0 ValueType for a SAML 1.1 token in the SecurityTokenReference/KeyIdentifier element

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?