Hi,
I honestly thought I had anonymous read access but it turns out SASL is
involved. As a test:
ldapsearch -b 'dc=test,dc=local' -H ldap://ldap001 cn=waynemerricks
I get:
SASL/DIGEST-MD5 authentication started
Please enter your password:
ldap_sasl_interactive_bind_s: Invalid credentials (49)
Hi,
I spun up a 14.04 VM to test this out as per the digitalocean guide.
sudo apt-get update
sudo apt-get install libpam-ldap nscd
Run through the ldap prompts as usual for my local server (basically the
defaults except for ldapi:/// becomes ldap:// etc)
Edit nsswitch:
passwd: ldap com
Apologies, was under the impression light-locker was handling the lock
screen. Thanks for the info
** Package changed: light-locker (Ubuntu) => unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Public bug reported:
After setting up LDAP authentication for user login. Users can log in
fine but as soon as the lock screen is activated, the user has to change
their password before they can unlock the screen.
First prompt is: Enter your password
Then: Enter your LDAP Password
Then: Enter ne
Affects light-locker (unity was selected for some reason)
** Package changed: unity (Ubuntu) => light-locker (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1323278
Title:
Ubuntu Lock Screen