PK83999: NamingException when updating group membership.

Fixes are available

APAR status

Closed as program error.

Error description

If cross-brand Ldap servers including AD Ldap are configured in
virtual member manager (VMM), update() API call with group
membership assignment may fail with NamingNotFoundException.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server v6.1 or v7.0 who use federated       *
*                  repositories (virtual member manager).      *
****************************************************************
* PROBLEM DESCRIPTION: If cross-brand Ldap including AD Ldap   *
*                      are configured in VMM, update() API     *
*                      call may fail with                      *
*                      NamingNotFoundException.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If cross-brand Ldap servers including AD Ldap were configured
in virtual member manager (VMM) as repositories, or both AD
Ldap and database repositories were configured at the same
time, the update() call with group membership in the other
brand Ldap server or database repository would fail with a
NamingException:

00000048 LdapConnectio 1
com.ibm.ws.wim.adapter.ldap.LdapConnection getRangeAttributes
Exception caught:
                                 javax.naming.NamingException:
[LDAP: error code 1 - 000020D6: SvcErr: DSID-03100684, problem
5012 (DIR_ERROR), data 0
 ]; remaining name 'cn=FS Admin,o=Default Organization'
 at com.sun.jndi.ldap.LdapCtx.mapErrorCode
(LdapCtx.java:3040)
 at com.sun.jndi.ldap.LdapCtx.c_getAttributes
(LdapCtx.java:1306)
......
 at
com.ibm.ws.wim.adapter.ldap.LdapConnection.getEntityByIdentifier
(LdapConnection.java:2276)
 at
com.ibm.ws.wim.adapter.ldap.LdapAdapter.get(LdapAdapter.java:134
8)       at
com.ibm.ws.wim.ProfileManager.getIdentifierByUniqueIdOrUniqueNam
e(ProfileManager.java:3851)
 at
com.ibm.ws.wim.ProfileManager.setExtIdAndRepositoryIdForEntities
(ProfileManager.java:3625)
 at
com.ibm.ws.wim.ProfileManager.updateImpl(ProfileManager.java:274
5).

Please note that the problem happened only when AD Ldap was
the first repository configured in VMM. For example, AD Ldap
was the first Ldap repository and then IDS Ldap was the second
repository configured in VMM. When assigning a user in IDS to
a group also in IDS as a group member, the update() call would
fail with the exception.

Problem conclusion

The problem has been fixed, there will be no exception thrown
for update() call with special scenario.
The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.27 and 7.0.0.5.  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
PK83999
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
60W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-02
Closed date
2009-04-14
Last modified date
2009-05-08

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 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":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK83999: NamingException when updating group membership.

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?