You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, when a user uses LDAP authentication, he should not be able to change is Username and Password.
Advantages of not letting the user change is credetials:
User will use a known credential. Less chances of losing the password.
When a member of staff leaves you can simply disable / delete the Active Directory account but the details will still be availible in Gogs.
I'm using a Bug Tracker named Mantis. Here is the UI with LDAP enabled and disabled:
They also have a setting to force the email address from the Active Directory ($g_use_ldap_email = ON;). In Gogs this would mean to disable changing the primary e-mail. But for now, this might be a problem because the primary e-mail is not retrieved on Active Directory.
They have another setting for the user Full Name ($g_use_ldap_realname = OFF;) in case we want LDAP to mange it. In that case the Full Name would also be disabled.
The text was updated successfully, but these errors were encountered:
Hi, when a user uses LDAP authentication, he should not be able to change is Username and Password.
Advantages of not letting the user change is credetials:
I'm using a Bug Tracker named Mantis. Here is the UI with LDAP enabled and disabled:
They also have a setting to force the email address from the Active Directory (
$g_use_ldap_email = ON;
). In Gogs this would mean to disable changing the primary e-mail. But for now, this might be a problem because the primary e-mail is not retrieved on Active Directory.They have another setting for the user Full Name (
$g_use_ldap_realname = OFF;
) in case we want LDAP to mange it. In that case the Full Name would also be disabled.The text was updated successfully, but these errors were encountered: