When constructs InitialLdapContext() failed, the detailed cause exception should be printed in the log by default

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.2.X EE, 7.0.X, Master
• Fix Version/s: 6.2.X EE, 7.0.0 DXP FP47, 7.0.0 DXP SP8, 7.0.X, 7.1.0 Beta 1, 7.1.X, Master
• Component/s: Application Security > LDAP
• Labels:
  • ee-ts
  • liferay-digital-enterprise-70-sp8
  • liferay-fixpack-de-47-7010
  • liferay-fixpack-portal-168-6210
• Branch Version/s:
  7.0.x, 6.2.x
• Backported to Branch:
  Committed
• Story Points: 5
• Git Pull Request: https://github.com/hhuijser/liferay-portal/pull/3254

Description:

The issue belongs to one improvement issue from user experience. When constructs an initial LDAP context, if it fails, the user hope can see the detailed cause reasons so that the user can check the issue better. 

Reproduction Steps:

1.  Set up one apache ldap.

2.  Go to Control Panel-> Configuration >Instances Settings>Authentication->LDAP, add one LDAP server.

3. Choose the Apache Directory Server.

4. Enter wrong connection info (wrong port number: 10) and then click "Test LDAP Connection".

Actual Behavior:

Only the infos "Liferay has failed to connect to the LDAP server. Please check your configuration and verify that the LDAP server is running." display in UI.

Expected Behavior:

 Besides UI infos display, the root exception should be printed in the log so that user can analyze the failure by using the detailed exception stack. For example, when input the port number "103898", the below infos should be printed in the log.

javax.naming.CommunicationException: localhost:103898 [Root exception is java.lang.IllegalArgumentException: port out of range:103898]