mirror of
https://github.com/processone/ejabberd.git
synced 2024-12-26 17:38:45 +01:00
Don't set fail_if_no_peer_cert for eldap ssl client connections
Looks like R26 generates error when this option is used for client connection, let's just use verify_peer/verify_none for ldap_tls_verify hard/soft options. This should fix issue #4110.
This commit is contained in:
parent
36fffa5b23
commit
c2d04bc478
@ -605,9 +605,9 @@ init([Hosts, Port, Rootdn, Passwd, Opts]) ->
|
||||
[]),
|
||||
CertOpts;
|
||||
Verify == soft ->
|
||||
[{verify, verify_peer}, {fail_if_no_peer_cert, false}] ++ CertOpts ++ CacertOpts ++ DepthOpts;
|
||||
[{verify, verify_none}] ++ CertOpts ++ CacertOpts ++ DepthOpts;
|
||||
Verify == hard ->
|
||||
[{verify, verify_peer}, {fail_if_no_peer_cert, true}] ++ CertOpts ++ CacertOpts ++ DepthOpts;
|
||||
[{verify, verify_peer}] ++ CertOpts ++ CacertOpts ++ DepthOpts;
|
||||
true -> []
|
||||
end,
|
||||
{ok, connecting,
|
||||
|
Loading…
Reference in New Issue
Block a user