-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.2.X, 7.3.X, Master
-
Fix Version/s: 7.2.X, 7.3.10 DXP FP1, 7.3.10.1 DXP SP1, 7.3.6 CE GA7, 7.3.X, 7.4.13 DXP GA1, Master
-
Component/s: Application Security > LDAP, Database Upgrade Framework
-
Branch Version/s:7.3.x, 7.2.x
-
Backported to Branch:Committed
-
Fix Priority:4
-
Git Pull Request:
Steps to Reproduce
- Start up a clean instance Liferay Portal 6.2
- Set up an LDAP authentication
- Navigate to Control Panel > Server Administration > Log Levels and set all classes related to LDAP to DEBUG
- Log in as an LDAP user
- Observe that in the DEBUG logs, the java.naming.provider.url listed includes the three connection settings set by default in portal.properties
java.naming.provider.url=ldap://localhost:10389, java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, com.sun.jndi.ldap.connect.timeout=500, com.sun.jndi.ldap.connect.pool=true, java.naming.security.principal=cn=ldapadmin,dc=example,dc=com, java.naming.security.credentials=*******, java.naming.referral=follow, *com.sun.jndi.ldap.read.timeout=15000}
- Shut down Liferay and upgrade the instance to DXP 7.2
- In DXP 7.2, navigate to Control Panel > Server Administration > Log Levels and set all classes related to LDAP to DEBUG
- Log in as an LDAP user
Expected Behavior: In the debug logs, the java.naming.provider.url also contains the three connection properties
Actual Behavior: In the debug logs, the java.naming.provider.url does not contain the three connection properties
java.naming.provider.url=ldap://localhost:10389, java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, java.naming.security.principal=cn=ldapadmin,dc=example,dc=com, java.naming.security.credentials=********, java.naming.referral=follow}