PM17024: USER REGISTRY CONFIGURED IN SECURITY DOMAIN MAY NOT BE USED AS EXPECTED.

Fixes are available

APAR status

Closed as program error.

Error description

User Registry configured in security domain may not be used as
expected.

When you configured the Domain Registry for JVM as example: IBM
Tivoli Directory, but user is trying search from MS Active
Directory that fails to find user.

It's trying to use Active Directory config to search the user,
but user does not exit in Active Directory, user should be
search using example IBM Tivoli Directory Server domain
registry.

00000028 PluggableAuth 3  getAuthorizationTableProxy using
domainId domain:AutenricacaoLdapIBM
00000028 PluggableAuth 3  getAuthorizationTableProxy did not
find PluggableAuthorizationTableProxy in cache
PluggableAuth >  createInstance,  domainId=domain:DomainLdapIBM
Entry
00000028 PluggableAuth 3   Pluggable Authz Table name: null
00000028 PluggableAuth <  createInstance Exit
                                  <null>

If we go back further in same thread we see that it searching
the MS AD
LDAP

00000028 LdapRegistryI 3   Searching for  users
00000028 LdapRegistryI >  getUsers Entry
                                cn=00001,ou=People,o=ibm
                                  2
00000028 LdapRegistryI >  search Entry
00000028 LdapRegistryI 3   DN: DC=ibm,DC=com
00000028 LdapRegistryI 3   Search scope: 2
00000028 LdapRegistryI 3   Filter:
(&(sAMAccountName=cn=00001,ou=People,o=ibm)(objectcategory=user
))

00000028 LdapRegistryI 3   try connect to ldap://ibm.com:389


00000028 LdapRegistryI 3   Number of users returned = 0
00000028 LdapRegistryI <  getUsers Exit
cn=00001,ou=People,o=ibm
                                  2
00000028 LdapRegistryI E   No user
cn=00001,ou=People,o=ibm found

So as you can see that it searching AD, oppose to IBM Tivoli
Directory.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server who configure a Security Domain      *
*                  and use Web Services or AynchBeans          *
*                  functionality.                              *
****************************************************************
* PROBLEM DESCRIPTION: The Configuration in a Security Domain  *
*                      may not be used in some Web Services    *
*                      and AsychBeans scenarios.               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In some scenarios involving Web Services and AsynchBeans,
a Security Domain configuration may be ignored.

Problem conclusion

The code was corrected to ensure that the Security Domain
configuration data is appropriately used.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.13.  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
PM17024
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-06-23
Closed date
2010-07-19
Last modified date
2010-07-19

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
WEBS APP SERV N
Fixed component ID
5724H8800

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:
24 October 2021

Tips

PM17024: USER REGISTRY CONFIGURED IN SECURITY DOMAIN MAY NOT BE USED AS EXPECTED.

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?