diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2018-01-03 10:00:08 -0500 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2018-01-03 10:11:26 -0500 |
| commit | 35c0754fadca8010955f6b10cb47af00bdbe1286 (patch) | |
| tree | 0df537278cc8998dbe29941d43833d95306e217e /src/backend/executor/nodeHash.c | |
| parent | 2268e6afd59649d6bf6d114a19e9c492d59b43fc (diff) | |
| download | postgresql-35c0754fadca8010955f6b10cb47af00bdbe1286.tar.gz postgresql-35c0754fadca8010955f6b10cb47af00bdbe1286.zip | |
Allow ldaps when using ldap authentication
While ldaptls=1 provides an RFC 4513 conforming way to do LDAP
authentication with TLS encryption, there was an earlier de facto
standard way to do LDAP over SSL called LDAPS. Even though it's not
enshrined in a standard, it's still widely used and sometimes required
by organizations' network policies. There seems to be no reason not to
support it when available in the client library. Therefore, add support
when using OpenLDAP 2.4+ or Windows. It can be configured with
ldapscheme=ldaps or ldapurl=ldaps://...
Add tests for both ways of requesting LDAPS and a test for the
pre-existing ldaptls=1. Modify the 001_auth.pl test for "diagnostic
messages", which was previously relying on the server rejecting
ldaptls=1.
Author: Thomas Munro
Reviewed-By: Peter Eisentraut
Discussion: https://postgr.es/m/CAEepm=1s+pA-LZUjQ-9GQz0Z4rX_eK=DFXAF1nBQ+ROPimuOYQ@mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeHash.c')
0 files changed, 0 insertions, 0 deletions