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
Here are a few notes on getting LDAPS working, with modern encryption.
Server certificate MUST be recognized by the operating system.
(We can download the certificate and convert to DER (.crt) format directly, using openssl.)
(Install the certificate in Windows using certmgr: Often you must "Browse" -> "Show physical locations" and save to "Trusted Root Certification Authorities\Registry" for it to work)
Evolution will not prompt to add an ad-hoc certificate for LDAP or CalDav as it does email images etc.
LDAPS TLS-elevation does not seem to work from the plain-text port (389)
LDAPS using TLS 1.x full-time encryption does work if port is specified as 636
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Here are a few notes on getting LDAPS working, with modern encryption.
Server certificate MUST be recognized by the operating system.
(We can download the certificate and convert to DER (.crt) format directly, using openssl.)
(Install the certificate in Windows using certmgr: Often you must "Browse" -> "Show physical locations" and save to "Trusted Root Certification Authorities\Registry" for it to work)
Evolution will not prompt to add an ad-hoc certificate for LDAP or CalDav as it does email images etc.
LDAPS TLS-elevation does not seem to work from the plain-text port (389)
LDAPS using TLS 1.x full-time encryption does work if port is specified as 636
Beta Was this translation helpful? Give feedback.
All reactions