PM01393: WS-SECURITY JAX-WS RUNTIME MUST REJECT SOME SAML TOKENS WITH SENDER-VOUCHES CONFIRMATION

Fixes are available

APAR status

Closed as program error.

Error description

Sender-vouches is listed as a limitation for WebSphere
Application Server WS-Security's support of SAML tokens.
However, the WS-Security runtime does not reject SOAP messages
containing SAML tokens with a sender-vouches confirmation
method.

SAML tokens with a sender-vouches confirmation method that is
not signed by the sender should be rejected.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
*                  of SAML sender-vouches assertion as the     *
*                  authentication token                        *
****************************************************************
* PROBLEM DESCRIPTION: JAX-WS WS-Security is accepting         *
*                      sender-vouches SAML assertions          *
*                      without validating if the               *
*                      assertion is vouched by sender          *
****************************************************************
* RECOMMENDATION:  Install a fix pack that contains this APAR. *
****************************************************************
JAX-WS WS-Security is accepting sender-vouches SAML assertions
without validating if the assertion is vouched by sender.

Problem conclusion

The JAX-WS WS-Security runtime is updated to support
sender-vouches SAML assertions in the following two common
scenarios:

Scenario 1. "sender-vouches SAML token" over SSL Client
Certificate.
The initiator adds the SAML token to the SOAP security header,
and uses client certificate authentication over SSL to protect
the message. In this scenario, SSL transport protection is
used.

Scenario 2: "sender-vouches SAML token" with X509Token, signed
and optionally encrypted.
In this scenario, a non-encrypted SAML assertion is indirectly
signed by using STR-TRANSFORM.

If a sender-vouches SAML assertion cannot be verified as
defined in one of the two scenarios, the SAML token will be
rejected.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  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
PM01393
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-11-16
Closed date
2009-12-17
Last modified date
2009-12-17

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

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM01393: WS-SECURITY JAX-WS RUNTIME MUST REJECT SOME SAML TOKENS WITH SENDER-VOUCHES CONFIRMATION

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

R700 PSY

Document Information

Share your feedback

Need support?