Troubleshooting
Problem
After upgrading to the fixpack WAS 8.5.5.25, this exception may be triggered during a failed login to the WebSphere Application Server admin console or an individual application when a special character is used in the domain name for the LDAP server.
SystemOut.log
Exception E com.ibm.ws.wim.adapter.ldap.LdapConnection getDirContext
com.ibm.websphere.wim.exception.WIMSystemException: CWWIM4520E The 'javax.naming.NamingException: Cannot parse url: ldap://ldap_server.example.com:389 [Root exception is java.net.MalformedURLException: unsupported authority:ldap_server.example.com:389]' naming exception occurred during processing.
at com.ibm.ws.wim.adapter.ldap.LdapConnection.getDirContext(LdapConnection.java:1878)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection.java:3323)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.checkSearchCache(LdapConnection.java:3241)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection.java:3439)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.searchEntities(LdapConnection.java:3675)
at com.ibm.ws.wim.adapter.ldap.LdapAdapter.login(LdapAdapter.java:3207)
at com.ibm.ws.wim.ProfileManager.loginImpl(ProfileManager.java:3864)
at com.ibm.ws.wim.ProfileManager.genericProfileManagerMethod(ProfileManager.java:365)
at com.ibm.ws.wim.ProfileManager.login(ProfileManager.java:478)
at com.ibm.websphere.wim.ServiceProvider.login(ServiceProvider.java:545)
at com.ibm.ws.wim.registry.util.LoginBridge.checkPassword(LoginBridge.java:194)
com.ibm.websphere.wim.exception.WIMSystemException: CWWIM4520E The 'javax.naming.NamingException: Cannot parse url: ldap://ldap_server.example.com:389 [Root exception is java.net.MalformedURLException: unsupported authority:ldap_server.example.com:389]' naming exception occurred during processing.
at com.ibm.ws.wim.adapter.ldap.LdapConnection.getDirContext(LdapConnection.java:1878)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection.java:3323)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.checkSearchCache(LdapConnection.java:3241)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection.java:3439)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.searchEntities(LdapConnection.java:3675)
at com.ibm.ws.wim.adapter.ldap.LdapAdapter.login(LdapAdapter.java:3207)
at com.ibm.ws.wim.ProfileManager.loginImpl(ProfileManager.java:3864)
at com.ibm.ws.wim.ProfileManager.genericProfileManagerMethod(ProfileManager.java:365)
at com.ibm.ws.wim.ProfileManager.login(ProfileManager.java:478)
at com.ibm.websphere.wim.ServiceProvider.login(ServiceProvider.java:545)
at com.ibm.ws.wim.registry.util.LoginBridge.checkPassword(LoginBridge.java:194)
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSAW57","label":"WebSphere Application Server Network Deployment"},"ARM Category":[{"code":"a8m50000000CdJaAAK","label":"WebSphere Application Server traditional-All Platforms-\u003ESecurity-\u003EAdministrative Security"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
16 July 2024
UID
ibm17160426