PK76687: FEDERATED LDAP REPOSITORY WITH SSL DOES NOT PICK UP A SPECIFIC SSL ALIAS

Fixes are available

APAR status

Closed as program error.

Error description

Federated LDAP repository with SSL does not work if a spefic SSL
alias is used. A connection to the LDAP fails even though the
store contains the certificates.
The application server seems to look for signer certificates in
the cell/node default trust store instead of the specified SSL
configuration alias, because adding the certificates to the
cell/node trust store makes the connection and authentication
succeed.
Standalone LDAP with the same SSL alias works fine.

Customer reported this problem in V6.1.0.17 .

Local fix

Disable SSL between federated repository and ldap registry.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V6.1 and V7.0 who use federated             *
*                  repositories (virtual member manager).      *
****************************************************************
* PROBLEM DESCRIPTION: Custom SSL configuration was not        *
*                      always used in a multiple threads       *
*                      application.                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In multi-threaded applications, custom SSL settings could not
always be used. The following exception is thrown if a custom
SSL configuration fails:

[10/14/08 10:06:49:479 CEST] 00000033 LdapConnectio 1
com.ibm.ws.wim.adapter.ldap.LdapConnection
createDirContext(String, byte[]) Exception caught:

javax.naming.CommunicationException: simple bind failed:
ldap.domain.com:636 [Root exception is
javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: No
trusted certificate found]
 at
com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:212)
 at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2652)
 at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:298)
 at
com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java
:190)
 at
com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.jav
a:208)
 at
com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFacto
ry.java:151)
 at
com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactor
y.java:81)
 at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.j
ava:679)
 at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.jav
a:259)
 at javax.naming.InitialContext.init
(InitialContext.java:235)
 at
javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.j
ava:146)
 at
com.ibm.ws.wim.adapter.ldap.TimedDirContext.<init>(TimedDirConte
xt.java:61)
 at
com.ibm.ws.wim.adapter.ldap.LdapConnection.createDirContext(Ldap
Connection.java:574)
 at
com.ibm.ws.wim.adapter.ldap.LdapAdapter.authenticateWithPassword
(LdapAdapter.java:2583)
 at
com.ibm.ws.wim.adapter.ldap.LdapAdapter.login(LdapAdapter.java:2
568)

Problem conclusion

The exception has been fixed. The custom SSL setting can be
used in multi-threaded applications with no problem.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.25 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
PK76687
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-12-01
Closed date
2008-12-15
Last modified date
2009-04-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.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK76687: FEDERATED LDAP REPOSITORY WITH SSL DOES NOT PICK UP A SPECIFIC SSL ALIAS

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?