PM47114: VMM DOES NOT HANDLE ROOT BASE ENTRIES FROM LDAP PROPERLY.

Fixes are available

APAR status

Closed as program error.

Error description

After migrating from WebSphere member manager (WMM) to virtual
member manager (VMM), VMM is not able to process/handle root
i.e BLANK base entries from LDAP.
VMM allows to configure root of the LDAP server to be configured
into VMM. WMM was allows BLANK names to baseEntries and was not
handled properly by VMM.

After migrating from WMM to VMM, VMM was showing nothing for
getIdMgrRepositoriesForRealm, output for the said command was
{}; i.e nothing.
And throws NullPointerException in WAS ISC.
java.lang.NullPointerException
at
com.ibm.ws.console.security.IdMgrRealm.VirtualRealmDetailActionG
en.popul
ateCollectionTableRow(VirtualRealmDetailActionGen.java:213)
at
com.ibm.ws.console.security.IdMgrRealm.VirtualRealmController.se
tupColle
ctionForm(VirtualRealmController.java:300)
at
com.ibm.ws.console.security.IdMgrRealm.VirtualRealmController.se
tupDetai
lForm(VirtualRealmController.java:208)
at
com.ibm.ws.console.core.action.BaseDetailController.perform(Base
DetailCo
ntroller.java:299)
at
org.apache.struts.tiles.TilesRequestProcessor.processTilesDefini
tion(Unk
nown Source)
at
org.apache.struts.tiles.TilesRequestProcessor.processForwardConf
ig(Unkno
wn Source)
at
com.ibm.isclite.container.controller.InformationController.proce
ssForwar
dConfig(InformationController.java:217)
at org.apache.struts.action.RequestProcessor.process(Unknown
Source)
at org.apache.struts.action.ActionServlet.process(Unknown
Source)
at org.apache.struts.action.ActionServlet.doPost(Unknown
Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
apper.ja
va:1657)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
apper.ja
va:1597)

Local fix

```
No workaround.
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0 and V8.0                        *
****************************************************************
* PROBLEM DESCRIPTION: After migrating from WMM to VMM, VMM    *
*                      is not able to process root (that is,   *
*                      BLANK) base entries from LDAP.          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
VMM allows you to configure "root"(BLANK baseentry in VMM) of
the LDAP server. But after migrating from WMM to VMM. VMM is
not able to process BLANK base entries from LDAP(root
baseEntry).

Problem conclusion

This fix will read BLANK baseEntry as ROOT and reflect the
same back to the configuration console/panels.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.21 and 8.0.0.2.  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
PM47114
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-04
Closed date
2011-11-29
Last modified date
2011-11-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

[{"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:
28 October 2021

Tips

PM47114: VMM DOES NOT HANDLE ROOT BASE ENTRIES FROM LDAP PROPERLY.

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

Document Information

Share your feedback

Need support?