Sourcetree login failed web proxy how to#
An LDAP filter declaring how to find the user record that is attempting toĪuthenticate.The LDAP base at which user accounts will be searched for.To ensure that the Bind DN has as few privileges as possible. Is stored encrypted with the SECRET_KEY on the server. The password for the Bind DN specified above, if any.
May be left blank to perform an anonymous search. The DN to bind to the LDAP server with when searching for the user.This will be used to populate their account information. The attribute of the user's LDAP record containing the user's emailĪddress.The attribute of the user's LDAP record containing the user's surname.The attribute of the user's LDAP record containing the user's first name.Example for Microsoft Active Directory (AD): sAMAccountName.This is useful when supplied login name is matched against multipleĪttributes, but only single specific attribute should be used for Gitea.Leave empty to use login name given on sign-in form. GivenĪttribute value will be used for new Gitea account user name after first The attribute of the user's LDAP record containing the user name.Example for Microsoft Active Directory (AD): (memberOf=CN=admin-group,OU=example,DC=example,DC=org).If a user account passes the filter, the user will be An LDAP filter specifying if a user should be given administrator.Whether to use TLS when connecting to the LDAP server.Example: 389 for LDAP or 636 for LDAP SSL.The port to use when connecting to the server.The address where the LDAP server can be reached.
A name to assign to the new method of authorization.Authentication LDAP (Lightweight Directory Access Protocol) īoth the LDAP via BindDN and the simple auth LDAP share the following fields:
0 kommentar(er)
