and more in a single search tool across platforms. Read the announcement here. |
06/20/2023 07:08 AM
We have an AD connection setup in our dev environment and it is working; however, the same AD connection using the LDAPS certificate in prod is not working. We have verified the parameters between the two environments are the same.
Do the two environments use the same certificate or are new certificates needed for each environments?
06/20/2023 07:53 AM
Hello @jdfranco ,
If the Dev and Prod servers are the same, you can use the same certificate. However, I would recommend validating the certificate.
Have you attempted to connect using the direct IP address through a non-SSL port? If so, is the error you're experiencing the same in that scenario as well?
For Ref :- https://forums.saviynt.com/t5/identity-governance/ad-connection-not-working-in-prod-setup/td-p/38630
06/20/2023 09:07 AM
No, with non-ssl and IP ldap://X.X.X.X:389/ connection is working fine
06/20/2023 08:43 PM
Hello @jdfranco,
Please provide the log snippet and analysis of the connection-saving and testing process for the following scenario:
Scenario to check:
1. Hostname using SSL port (636)
2. Hostname using Non-SSL port (389)
3. IP using SSL port (636)
Thanks,
06/23/2023 06:54 AM
07/06/2023 03:38 AM
Hello @jdfranco,
This is the DNS issue, could you please verify if the hostname details are added in the DNS?
Thanks,