Hi Jon,
LAMS supports -by default, three different ways of authentication users:
LAMS Database: these are users that were created in LAMS directly (no external user database involved)
Web-Auth: an external system that was a predecessor of OpenID and I'm doubt that anyone use these days -but it's there
LDAP: as you guys do, using an external LDAP server for authentication.
(Note that we also support OpenID and SAML2 using other LAMS modules).
What these means is that if the user was created via LDAP, then the authentication module will be LDAP. So when the user comes to the login page and attempts a login, LAMS will send the details to the LDAP server to validate them.
If the user is a local user (LAMS Database), LAMS will check with its own user records to validate the user.
Now if I understand you correctly, you are saying that a user that you created manually in LAMS (which should default to LAMS Database authentication) it shows -when you edit his/her details as LDAP Authentication. Is this correct?
If so, it could be that the user login that you use to create it with in LAMS was the exact same as the one it has in LDAP. So when a sysadmin does a LDAP synchronization, then the Authentication method for this user would be overwrite and set to LDAP authentication instead.
Is this the case?
If not, let me know because this can potentially be a bug.
Thanks,
Ernie
Posted by Ernie Ghiglione