IBM Support

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

Fixes are available

7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM17024

Modified date: 19 July 2010