PM69064: SAML WEB SSO DOES NOT RECOGNIZE UPDATES TO CENTRALIZED KEYSTORES

Fixes are available

APAR status

Closed as program error.

Error description

When the SAML Web SSO TAI ACSTrustAssociationInterceptor uses
the Cell Level default trust store for signer certificates,
after the server is started, any signer certificate added to
the trust store are not picked up immediately.  If a valid SAML
response is sent that was signed by the certificate that was
just added, the request is rejected. When the server is
restarted, the request will be successful.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server            *
*                  administrators of WS-Security enabled       *
*                  JAX-WS applications and SAML Web SSO TAI    *
****************************************************************
* PROBLEM DESCRIPTION: WS-Security and SAML Web SSO do not     *
*                      recognize updates to centralized        *
*                      keystores                               *
****************************************************************
* RECOMMENDATION:  Install a fix pack that contains this       *
*                  APAR.                                       *
****************************************************************
When an application is configured to use a centralized
keystore for its trust store, when certificates are added or
deleted from the keystore, the updates are not recognized by
the application.
For instance, a WS-Security enabled JAX-WS application is
configured with a centralized keystore in its X.509 callback
handler for digital signature.  If a certificate is added to
the keystore, a message that is signed with that certificate
will be rejected because it is not trusted.
Another example: The ACSTrustAssociationInterceptor is
configured with a centralized keystore for its trust store.
If a certificate is deleted from the keystore, a message that
is signed with that certificate will not be rejected, but it
should be.
When the application server is restarted, updates to the
centralized keystore are recognized by the applications and
the trust evaluation behaves as expected.
This APAR does not apply to hardcoded keystores.  Updates to
hardcoded keystores are not intended to be recognized until
the application server is restarted.

Problem conclusion

When a centralized keystore is opened by the runtime, an
instance of the object is cached.  When the keystore is
modified, the WebSphere runtime creates a new object instead
of updating the original object, so the object that was cached
has become obsolete.

The runtime is updated to not cache the keystore objects for
centralized keystores.

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

Keywords: IBMWL3WSS, SAMLWSSO

Temporary fix

Comments

APAR Information

APAR number
PM69064
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-07-17
Closed date
2012-07-24
Last modified date
2015-10-29

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
R800 PSY
UP
R850 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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021

Tips

PM69064: SAML WEB SSO DOES NOT RECOGNIZE UPDATES TO CENTRALIZED KEYSTORES

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?