PM30396: THREAD IDENTITY NOT PROPOGATED TO CICS WHEN USER REGISTRY IS lDAP

Fixes are available

APAR status

Closed as program error.

Error description

When running WebSphere Application Server zOS, the
Application prompted userid/password (thread identity) is not
propagated into CICS.

The server userid was used instead to make the connection with
CICS.

'Enable the connection manager RunAs thread identity' was
Checked.

CICS J2EE ECI Resource Adapter (cicseci.rar) was used in this
case for zWAS -> CICS connection.

No exceptions were observed in this reported situation, as the
server id used to make the connection was a valid CICS user.

This error is encountered when the User Registry is configured
to use LDAP.  If the User Registry is switched to Local OS then
the error is not encountered.

Local fix

This error can be avoided by switching User Registries from LDAP
to Local OS.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V8.0                        *
****************************************************************
* PROBLEM DESCRIPTION: Thread Identity not propagated to       *
*                      CICS when user registry is configured   *
*                      to LDAP & SAF Authorization enabled     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
ThreadIdentitySecurityHelper which houses all the thread
identiy related functionalities was being created only when
the underlying resource adapter's ThreadIdentitySupport is
"ALLOWED" or "REQUIRED" and the configured user registry is
local OS.

When non-Local OS user registry(i.e LDAP) is configured,
DefaultSecurityHelper class will be created hence thread
identity support will not be enabled.

However with non-Local OS user registry(i.e LDAP), if
SAF Authorization is enabled and mapping between the
LDAP identity and the z/OS identity exists, still
DefaultSecurityHelper was being created, which is incorrect
and caused the thread identity not propagate to CICS.

Problem conclusion

WebSphere J2C component has been corrected to use the
appropriate security helper class.

APAR PM30396 is currently targeted for inclusion in Service
Level (Fix Pack) 6.1.0.41 of WebSphere Application Server V6.1.
and Fix Pack 8.0.0.1 of WebSphere Application Server V8.0.

Sysroute APAR PM34251 will be used to deliver this fix in
WebSphere Application Server V7.0.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PM30396
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-01-12
Closed date
2011-05-10
Last modified date
2011-12-02

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

PM34251

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R610 PSY UK73054
UP11/11/03 P F111

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

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

Document Information

Modified date:
27 October 2021

Tips

PM30396: THREAD IDENTITY NOT PROPOGATED TO CICS WHEN USER REGISTRY IS lDAP

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

R610 PSY UK73054

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?