You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Investigation showed the certificate CN of each host did actually match its hostname. It also showed the application was able to connect to each of these hosts when configured directly as a single server:
host: 'host1.ourdomain.com',
port: 636,
Other workarounds I identified:
Setting verify_mode=OpenSSL::SSL::VERIFY_NONE, though this is not recommended
Reverting net-ldap to v0.17.1
The text was updated successfully, but these errors were encountered:
net-ldap version 0.18.0
LDAP server version: Windows Active Directory (unsure of specific version)
OpenSSL version: OpenSSL 1.0.2k-fips 26 Jan 2017
I upgraded from net-ldap v0.17.1 to 0.18.0 to find our Rails app could no longer connect to our LDAP server:
Our (unchanged) LDAP configuration uses an array of hosts, like this:
Investigation showed the certificate CN of each host did actually match its hostname. It also showed the application was able to connect to each of these hosts when configured directly as a single server:
Other workarounds I identified:
verify_mode=OpenSSL::SSL::VERIFY_NONE
, though this is not recommendedThe text was updated successfully, but these errors were encountered: