From f32a3776d4ce94bbc67bcaa10f878f6efc7f7439 Mon Sep 17 00:00:00 2001 From: Ramkumar K Date: Thu, 30 May 2024 13:19:30 +0530 Subject: [PATCH] 7339-OL-configured-TAI-reword-1 7339-OL-configured-TAI-reword-1 #7339 --- modules/ROOT/pages/troubleshooting.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/modules/ROOT/pages/troubleshooting.adoc b/modules/ROOT/pages/troubleshooting.adoc index ec83ea9a1..2f503652d 100644 --- a/modules/ROOT/pages/troubleshooting.adoc +++ b/modules/ROOT/pages/troubleshooting.adoc @@ -276,7 +276,8 @@ If you use a minimal TLS configuration, set the `ID` field to `defaultKeyStore`. [#Troubleshooting_TAI] == Troubleshooting Trust Association Interceptor -When the `TrustAssociationInterceptor` component calls the `InitialDirContext` class with the Java property `java.naming.ldap.factory.socket` set to a socket factory other than `LibertySSLSocketFactory` (such as `com.ibm.ws.ssl.LibertySSLSocketFactoryWrapper`), a `NoClassDefFoundException` occurs. This issue is particularly challenging to debug and typically requires the expertise of both the security and classloader teams. +To avoid potential issues, users must not configure the `TrustAssociationInterceptor` component to call the `InitialDirContext` class with the Java property `java.naming.ldap.factory.socket` set to a socket factory other than Liberty's own (`com.ibm.ws.ssl.protocol.LibertySSLSocketFactory`). Setting this property to other factories can cause a `NoClassDefFoundException`. + [#Other_troubleshooting] == Other troubleshooting issues