Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
8fd40def
Commit
8fd40def
authored
Sep 14, 2018
by
Drew Blessing
Committed by
Achilleas Pipinellis
Sep 14, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update sync Cron example to be more realistic
parent
760ee63f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
9 deletions
+9
-9
doc/administration/auth/ldap-ee.md
doc/administration/auth/ldap-ee.md
+9
-9
No files found.
doc/administration/auth/ldap-ee.md
View file @
8fd40def
...
@@ -61,7 +61,7 @@ NOTE: **Note:**
...
@@ -61,7 +61,7 @@ NOTE: **Note:**
The LDAP sync process updates existing users while new users will
The LDAP sync process updates existing users while new users will
be created on first sign in.
be created on first sign in.
## Group Sync
**[PREMIUM ONLY]**
## Group Sync
If your LDAP supports the
`memberof`
property, GitLab will add the user to any
If your LDAP supports the
`memberof`
property, GitLab will add the user to any
new groups they might be added to when the user logs in. That way they don't need
new groups they might be added to when the user logs in. That way they don't need
...
@@ -195,14 +195,15 @@ By default, GitLab will run a worker once per day at 01:30 a.m. server time to
...
@@ -195,14 +195,15 @@ By default, GitLab will run a worker once per day at 01:30 a.m. server time to
check and update GitLab users against LDAP.
check and update GitLab users against LDAP.
You can manually configure LDAP user sync times by setting the
You can manually configure LDAP user sync times by setting the
following configuration values.
following configuration values. The example below shows how to set LDAP user
sync to run once every 12 hours at the top of the hour.
**Omnibus installations**
**Omnibus installations**
1.
Edit
`/etc/gitlab/gitlab.rb`
:
1.
Edit
`/etc/gitlab/gitlab.rb`
:
```ruby
```ruby
gitlab_rails['ldap_sync_worker_cron'] = "
*
*/12 * * *"
gitlab_rails['ldap_sync_worker_cron'] = "
0
*/12 * * *"
```
```
1.
[
Reconfigure GitLab
](
../restart_gitlab.md#omnibus-gitlab-reconfigure
)
for the changes to take effect.
1.
[
Reconfigure GitLab
](
../restart_gitlab.md#omnibus-gitlab-reconfigure
)
for the changes to take effect.
...
@@ -214,15 +215,13 @@ following configuration values.
...
@@ -214,15 +215,13 @@ following configuration values.
```yaml
```yaml
cron_jobs:
cron_jobs:
ldap_sync_worker_cron:
ldap_sync_worker_cron:
"
*
*/12 * * *"
"
0
*/12 * * *"
```
```
1.
[
Restart GitLab
](
../restart_gitlab.md#installations-from-source
)
for the changes to take effect.
1.
[
Restart GitLab
](
../restart_gitlab.md#installations-from-source
)
for the changes to take effect.
## Adjusting LDAP group sync schedule
## Adjusting LDAP group sync schedule
> Introduced in GitLab Enterprise Edition Premium.
NOTE:
**Note:**
NOTE:
**Note:**
These are cron formatted values. You can use a crontab generator to create
These are cron formatted values. You can use a crontab generator to create
these values, for example http://www.crontabgenerator.com/.
these values, for example http://www.crontabgenerator.com/.
...
@@ -230,21 +229,22 @@ these values, for example http://www.crontabgenerator.com/.
...
@@ -230,21 +229,22 @@ these values, for example http://www.crontabgenerator.com/.
By default, GitLab will run a group sync process every hour, on the hour.
By default, GitLab will run a group sync process every hour, on the hour.
CAUTION:
**Important:**
CAUTION:
**Important:**
It's recommended
not to run group sync at
too short intervals as this
It's recommended
that you do not run
too short intervals as this
could lead to multiple syncs running concurrently. This is primarily a concern
could lead to multiple syncs running concurrently. This is primarily a concern
for installations with a large number of LDAP users. Please review the
for installations with a large number of LDAP users. Please review the
[
LDAP group sync benchmark metrics
](
#benchmarks
)
to see how
[
LDAP group sync benchmark metrics
](
#benchmarks
)
to see how
your installation compares before proceeding.
your installation compares before proceeding.
You can manually configure LDAP group sync times by setting the
You can manually configure LDAP group sync times by setting the
following configuration values.
following configuration values. The example below shows how to set group
sync to run once every 2 hours at the top of the hour.
**Omnibus installations**
**Omnibus installations**
1.
Edit
`/etc/gitlab/gitlab.rb`
:
1.
Edit
`/etc/gitlab/gitlab.rb`
:
```ruby
```ruby
gitlab_rails['ldap_group_sync_worker_cron'] = "
*/30
* * * *"
gitlab_rails['ldap_group_sync_worker_cron'] = "
0 */2
* * * *"
```
```
1.
[
Reconfigure GitLab
](
../restart_gitlab.md#omnibus-gitlab-reconfigure
)
for the changes to take effect.
1.
[
Reconfigure GitLab
](
../restart_gitlab.md#omnibus-gitlab-reconfigure
)
for the changes to take effect.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment