Nulo/forgejo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update docs for LDAP (via BindDN) user sync option. (#2985)

Browse source
This commit is contained in:
Mike Fellows 2017-11-30 05:36:53 -08:00 committed by Lunny Xiao
parent 474dfcc798
commit 82e8486f13
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/content/doc/features/authentication.en-us.md
View file

@ -95,6 +95,17 @@ Both the LDAP via BindDN and the simple auth LDAP share the following fields:
matching supplied login name against multiple attributes such as user matching supplied login name against multiple attributes such as user
identifier, email or even phone number. identifier, email or even phone number.
- Example: `(&(objectClass=Person)(|(uid=%[1]s)(mail=%[1]s)(mobile=%[1]s)))` - Example: `(&(objectClass=Person)(|(uid=%[1]s)(mail=%[1]s)(mobile=%[1]s)))`
- Enable user synchronization
- This option enables a periodic task that synchronizes the Gitea users with
the LDAP server. The default period is every 24 hours but that can be
changed in the app.ini file. See the *cron.sync_external_users* section in
the [sample
app.ini](https://github.com/go-gitea/gitea/blob/master/custom/conf/app.ini.sample)
for detailed comments about that section. The *User Search Base* and *User
Filter* settings described above will limit which users can use Gitea and
which users will be synchronized. When initially run the task will create
all LDAP users that match the given settings so take care if working with
large Enterprise LDAP directories.
**LDAP using simple auth** adds the following fields: **LDAP using simple auth** adds the following fields: