Troubleshoooting LDAP - Revision history

IVSWikiBlue at 22:22, 25 March 2025

2025-03-25T22:22:32Z

IVSWikiBlue at 22:22, 25 March 2025

2025-03-25T22:22:16Z

IVSWikiBlue at 20:53, 19 March 2025

2025-03-19T20:53:45Z

IVSWikiBlue at 16:03, 15 January 2025

2025-01-15T16:03:07Z

IVSWikiBlue at 13:34, 1 November 2024

2024-11-01T13:34:13Z

IVSWikiBlue at 16:01, 1 April 2024

2024-04-01T16:01:51Z

IVSWikiBlue at 16:01, 1 April 2024

2024-04-01T16:01:09Z

IVSWikiBlue at 16:00, 1 April 2024

2024-04-01T16:00:08Z

IVSWikiBlue at 15:56, 1 April 2024

2024-04-01T15:56:30Z

IVSWikiBlue at 15:56, 1 April 2024

2024-04-01T15:56:16Z

@@ Line 20: / Line 20: @@
 <hr>
-==Validate LDAP Query/Credentialswith ldapsearch==
+==Validate LDAP Query/Credentials with ldapsearch==
 After verifying communication between the VALT server and the LDAP server, you can validate the credentials you were provided by attempting to connect to the LDAP server from the command line.
 # Connect to the VALT server via SSH or access the terminal.

@@ Line 20: / Line 20: @@
 <hr>
-==Validate LDAP Query/Credentials==
+==Validate LDAP Query/Credentialswith ldapsearch==
 After verifying communication between the VALT server and the LDAP server, you can validate the credentials you were provided by attempting to connect to the LDAP server from the command line.
 # Connect to the VALT server via SSH or access the terminal.

← Older revision		Revision as of 20:53, 19 March 2025
Line 152:		Line 152:
	Using another special character check out [https://www.urlencoder.org/ this website] to get the correct format		Using another special character check out [https://www.urlencoder.org/ this website] to get the correct format

−	~~{{Aside \| content = To see an example, [{{filepath:LdapJarDebug.png}} click here].}}~~
	<hr>		<hr>

@@ Line 2: / Line 2: @@
 Note that this page pertains to troubleshooting LDAP for VALT 5.x versions.}}
 __TOC__
-{{Article | content =
+{{Article | title = Troubleshoooting LDAP | content =
 <div class="floating_card">Often times, configuring the VALT appliance for LDAP authentication can prove challenging. Most often these issues are caused by communications problems, incorrect credentials or using the wrong distinguished name. In order to troubleshoot the issue, it's recommended you take the VALT application out of the equation.</div>
-=Validate Connection=
+==Validate Connection==
 # Connect to the VALT server via SSH or access the terminal.
 #: ''If accessing via the terminal, you will need to exit to Shell.''
@@ Line 20: / Line 20: @@
 <hr>
-=Validate LDAP Query/Credentials=
+==Validate LDAP Query/Credentials==
 After verifying communication between the VALT server and the LDAP server, you can validate the credentials you were provided by attempting to connect to the LDAP server from the command line.
 # Connect to the VALT server via SSH or access the terminal.
@@ Line 43: / Line 43: @@
 <hr>
-=Validate LDAP Server Database Entry=
+==Validate LDAP Server Database Entry==
 If the Server and Credentials are correct, make sure that the database entry has the correct information
 # Go to the phpmyadmin interface for the server <code>http://<b><server_ip></b>/phpmyadmin</code>
@@ Line 51: / Line 51: @@
 <hr>
-=Verify Distinguished Name of Groups=
+==Verify Distinguished Name of Groups==
 If you believe the distinguished name of the group is incorrect, you can verify it by accessing the customer's directory using [http://www.ldapadmin.org/ LDAP Admin] and the credentials they have provided you.
 # Download and run LDAP Admin.
@@ Line 74: / Line 74: @@
 <hr>
-=LDAPS Security Certificate=
+==LDAPS Security Certificate==
 If you are connecting over LDAPS, you may experience an issue with security certificate presented by the LDAP server being untrusted by the VALT appliance.
 ===Verify the Issue===
@@ Line 100: / Line 100: @@
 <hr>
-=TLS 1.2 Issues=
+==TLS 1.2 Issues==
 There is a known compatibility issue between OpenLDAP and certain versions of Windows Server. This issue was resolved in hotfixes, however you if you are able to verify all the information is correct and you are still unable to submit an LDAP query via LDAPS, this may be the cause. The issue stems from a compatibility problem related to TLS 1.2. By disabling TLS version 1.2, you can force LDAPS to use TLS version 1.1.
@@ Line 125: / Line 125: @@
 <hr>
-=Unable to Connect to MYSQL Database=
+==Unable to Connect to MYSQL Database==
 This issue can occur after updating VALT to version 5.2 if the MySql config has been changed to listen on an interface other than the loopback address. This is not a common config, however this has been done in the past on several VALT implementations in order to allow customers to access the database directly to run queries or reports.
@@ Line 139: / Line 139: @@
 <hr>
-=LDAP Jar Debug=
+==LDAP Jar Debug==
 The below commands are used to help troubleshoot LDAP issues. You will need to substitute the correct information into the string in order for the command to function properly.
@@ Line 155: / Line 155: @@
 <hr>
-=Disable LDAPS SSL Check=
+==Disable LDAPS SSL Check==
 #Enter the below string at the bottom of <pre>/var/www/v3/app/config/parameters.yml</pre>
   disable_ldaps_ssl_check: true
 }}

← Older revision		Revision as of 13:34, 1 November 2024
Line 1:		Line 1:
		+	{{Aside \| content =
		+	Note that this page pertains to troubleshooting LDAP for VALT 5.x versions.}}
	__TOC__		__TOC__
	{{Article \| content =		{{Article \| content =

@@ Line 1: / Line 1: @@
-__NOTOC__
+__TOC__
 {{Article | content =
 <div class="floating_card">Often times, configuring the VALT appliance for LDAP authentication can prove challenging. Most often these issues are caused by communications problems, incorrect credentials or using the wrong distinguished name. In order to troubleshoot the issue, it's recommended you take the VALT application out of the equation.</div>
@@ Line 33: / Line 33: @@
 # The query should return a list of group members.
 #* If a list of group members was returned successfully, then LDAP authentication should be working. If you are still experiencing issues, it is most likely a configuration problem with the application.
-#*: {{img - resize | file = LDAPT1.png}}
+#*: {{img | file = LDAPT1.png}}
 #* If you received a message stating '''No Such Object''', the distinguished name of the group you entered is incorrect. The next section contains information on verifying the distinguished name or the group, or you can contact the customer's IT department.
-#*: {{img - resize | file = LDAPT3.png}}
+#*: {{img | file = LDAPT3.png}}
 #* If you received a message stating '''Invalid credentials''', the username or password you entered is incorrect. You will need to contact the customer's IT department.
-#*: {{img - resize | file = LDAPT2.png}}
+#*: {{img | file = LDAPT2.png}}
 <hr>
@@ Line 52: / Line 52: @@
 If you believe the distinguished name of the group is incorrect, you can verify it by accessing the customer's directory using [http://www.ldapadmin.org/ LDAP Admin] and the credentials they have provided you.
 # Download and run LDAP Admin.
-#: {{img - resize | file = LDAPT6.png}}
+#: {{img | file = LDAPT6.png | width=800px}}
 # Click '''Connect'''.
-#: {{img - resize | file = LDAPT7.png}}
+#: {{img | file = LDAPT7.png}}
 # Double click on '''New Connection'''.
-#: {{img - resize | file = LDAPT5.png}}
+#: {{img | file = LDAPT5.png}}
 # Enter the host.
 # Uncheck '''Anonymous Connection'''.
@@ Line 63: / Line 63: @@
 # Select the Base DN for the domain.
 #: EX: DC=internal,DC=ipivs,DC=com
-#: {{img - resize | file = LDAPT8.png}}
+#: {{img | file = LDAPT8.png}}
 # Click '''OK'''.
 # You can now browse the customer's directory. Using the distinguished name you were provided, try to locate the group.
-#: {{img - resize | file = LDAPT10.png | width=800px}}
+#: {{img | file = LDAPT10.png | width=800px}}
 #* If you are able to locate the group, click on the group, and the DN will be displayed on the right hand side of the window.
 #* If you are unable to locate the group, contact the customer's IT department.