mirror of
				https://gitee.com/gitea/gitea
				synced 2025-11-04 08:30:25 +08:00 
			
		
		
		
	LDAP: Optional user name attribute specification
Consider following LDAP search query example:
    (&(objectClass=Person)(|(uid=%s)(mail=%s)))
Right now on first login attempt Gogs will use the text supplied on login form
as the newly created user name. In example query above the text matches against
both e-mail or user name. So if user puts the e-mail then the new Gogs user
name will be e-mail which may be undesired.
Using optional user name attribute setting we can explicitly say we want Gogs
user name to be certain LDAP attribute eg. `uid`, so even user will use e-mail
to login 1st time, the new account will receive correct user name.
			
			
This commit is contained in:
		@@ -878,6 +878,8 @@ auths.bind_password = Bind Password
 | 
			
		||||
auths.bind_password_helper = Warning: This password is stored in plain text. Do not use a high privileged account.
 | 
			
		||||
auths.user_base = User Search Base
 | 
			
		||||
auths.user_dn = User DN
 | 
			
		||||
auths.attribute_username = Username attribute
 | 
			
		||||
auths.attribute_username_placeholder = Leave empty to use sign-in form field value for user name.
 | 
			
		||||
auths.attribute_name = First name attribute
 | 
			
		||||
auths.attribute_surname = Surname attribute
 | 
			
		||||
auths.attribute_mail = E-mail attribute
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user