![]() This was very useful, as it shows the dwExchStrength=2048 bit. ![]() However, I did not know about the LDAP_OPT_SSL_INFO option in LDP. I don't see any LDAP interface errors at all in my Directory Services event log, which isn't surprising as I don't think there is anything wrong. That I create will show up here as well, obviously. There are numerous connections on port 636, which I had checked after installing the new certificate and restarting the server (I don't use the AD service certificate store, so the reboot was necessary, even though the DCs are 2008+). My question is: is there a way to see what certificate is being used to allow port 636 SSL traffic? I'm pretty sure that this is an application issue, but want to ensure that it's not a certificate problem. Is retrieving the VeriSignA certificate when searching for certificates on port 636.) CertX is in the Certificates (Local Computer) -> Personal -> Certificates folder. Sitting in the Certificates (Local Computer) -> Personal -> Certificates folder. The certificates that this application are finding are the intermediary VeriSign certificates that signed the actual server certificate However, we have one application that needs to find a certificate presented on port 636 in order to use LDAPS connections. I can use LDP and create a connection on port 636 and it retrieves the RootDSE information as it should, so it appears that things are working as they should. These certificates are located in the Certificates (Local Computer) -> Personal -> Certificates folder on each domainĬontroller. We have VeriSign certificates on our domain controllers so that people can make LDAPS (secure LDAP) connections on port 636.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |