bind_policy hard broken in ldap.conf in 17.10
Bug #1732735 reported by
Reinhard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ldap-auth-client (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
A scripted installation of an ldap-client WORKING in ubuntu 16.04 is broken in ubuntu 17.10.
In ldap.conf:
host ldap01 ldap02 (was working in 16.04)
has to be replaced with:
host 10.0.0.9 10.0.0.10
otherwise the system stays in an endless loop at boot up!
Change from hostname to ip has to be done with a rescue system.
summary: |
- bind_policy hard broken in ldap.conf + bind_policy hard broken in ldap.conf in 17.10 |
To post a comment you must log in.
Did more testing in Ubuntu 17.10:
in ldap.conf:
host 10.0.0.9 10.0.0.10 => IP is working
host ldap01 ldap02 => hostname is NOT working
host ldap01.app.tsn => FQHN is NOT working
and NOT working does not mean that just ldap is broken, it means pc stays in endless boot loop
:-(