How to migrate from LDAP:389 to LDAPS:636 for user password reset with Crowd and Atlassian tools on a new DC

Question:

How to configure LDAPS:636 for a new DC with Crowd and Atlassian tools?

I have recently set up a new DC and I want to use LDAPS:636 to connect it with my crowd server and authenticate users. This was working fine with my old DC, but with the new one, I can only use LDAP:389, which does not allow users to reset their passwords. I have followed the steps from Atlassian to import the new certificate and update the keystroke, but I still get an error message when I test the connection from crowd. I am running Linux for my Atlassian tools and Windows Server 2022 for my DC. What could be the cause of this issue and how can I fix it? The error message is in the comments section.

Answer:

How to configure LDAPS:636 for a new DC with Crowd and Atlassian tools?

I have recently set up a new DC and I want to use LDAPS:636 to connect it with my crowd server and authenticate users. This was working fine with my old DC, but with the new one, I can only use LDAP:389, which does not allow users to reset their passwords. I have followed the steps from Atlassian to import the new certificate and update the keystroke, but I still get an error message when I test the connection from crowd. I am running Linux for my Atlassian tools and Windows Server 2022 for my DC. What could be the cause of this issue and how can I fix it? The error message is in the comments section.

Leave a Reply

Your email address will not be published. Required fields are marked *

Privacy Terms Contacts About Us