Portal v6.1.x: After enabling LDAP security, Portal fails to start with EJPSB0107E exception[@more@]
|
| | | Problem(Abstract) | | After enabling standalone LDAP security in IBM® WebSphere® Portal v6.1, the WebSphere_Portal server fails to start correctly. EJPSB0107E exceptions can be seen. | | | | Symptom | | The full exception in the SystemOut.log is:
=============================
[11/3/08 22:19:47:631 EST] 00000016 Servlet E com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of service failed.
com.ibm.wps.ac.DomainAdministratorNotFoundException: EJPSB0107E: Exception occurred while retrieving the identity of the domain admin user/admingroup cn=wpsadmins.
at com.ibm.wps.ac.impl.AccessControlDataManagementServiceImpl.convertDNtoObjectID(AccessControlDataManagementServiceImpl.java:987)
at com.ibm.wps.ac.impl.AccessControlDataManagementServiceImpl.access$000(AccessControlDataManagementServiceImpl.java:74)
at com.ibm.wps.ac.impl.AccessControlDataManagementServiceImpl$1.run(AccessControlDataManagementServiceImpl.java:890)
.
.
.
Caused by: com.ibm.wps.um.exceptions.impl.MemberNotFoundExceptionImpl: com.ibm.portal.puma.MemberNotFoundException: EJPSG0002E: Requested Member does not exist.cn=wpsadmins/null
at com.ibm.wps.um.VMMExceptionHelper.rethrowSystemMNF(VMMExceptionHelper.java:221)
at com.ibm.wps.um.PumaEngineHelper.loadWithBaseAttributes(PumaEngineHelper.java:688)
at com.ibm.wps.um.PumaLocatorImpl.findGroupByIdentifier(PumaLocatorImpl.java:368)
===============================
| | |
|
 |
|
| Cause |
In this particular case, the member that cannot be found is the Portal Admin Group ID. When enabling standalone ldap security, incorrect values for standalone.ldap.baseDN and standalone.ldap.groupParent will cause this issue.
VMM depends on these entries as base starting point when it validates the users. For example, if you set the following entries:
standalone.ldap.baseDN=o=mycompany
standalone.ldap.groupParent=o=mycompany
Then your Portal Admin ID and Portal Admin Group ID must exist in the "o=mycompany" tree. |
| |
|
| Resolving the problem |
To resolve this issue, complete the following steps:
1. Ensure that the values for standalone.ldap.baseDN and standalone.ldap.groupParent are accurate for the value you set for your Portal Administrative Group ID.
2. Execute the following ConfigEngine script:
./ConfigEngine.sh wp-modify-ldap-security 3. Restart the WebSphere_Portal server. |
| |
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/7199667/viewspace-1022532/
，如需转载，请注明出处，否则将追究法律责任。
