Here's an example of why you keep documentation current:
The test system has LDAP connectivity to adldap.organization through SSL. The CN of the certificate is listed in the web inteface as adldap.organization.
I can't successfully get through the setup wizard on my production system using the Org's Root CA. As far as everyone is aware - it was set up using the Root CA previously.
The Root CA is in the Java keystore on the production server
Jamf's reply was confusing - Article however adldap.org has the Root CA in it.
Is the web interface simply showing the CA as adldap.org because it's reading the root ca from that box?
Short version - Why would the internal Root CA not be accepted? It gives - "UNABLE TO COMMUNICATE WITH THE LDAP SERVER
Verify your configuration and try again"
There is connectivity. I verified from the box using an ldp connection .exe utility
The org is heavily siloed so I'm on my own
