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
e713922b
Commit
e713922b
authored
Dec 02, 2014
by
Job van der Voort
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
improve ldap sync documentation
parent
8e4a7eb4
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/integration/ldap.md
doc/integration/ldap.md
+2
-2
No files found.
doc/integration/ldap.md
View file @
e713922b
...
...
@@ -293,12 +293,12 @@ LDAP membership is checked for a GitLab user:
-
when they sign in to the GitLab instance
-
on a daily basis
-
on any request that they do, once the LDAP cache has expired (default 1 hour, configurable,
see below
)
-
on any request that they do, once the LDAP cache has expired (default 1 hour, configurable,
cache is per user
)
If you want a shorter or longer LDAP sync time, you can easily set this with the
`sync_time`
attribute in your config.
For Omnibus package installations, simply add
`"sync_time"`
in
`/etc/gitlab/gitlab.rb`
to your LDAP config.
A typical LDAP configuration might look like this:
A typical LDAP configuration
for GitLab installed with an Omnibus package
might look like this:
```
gitlab_rails['ldap_servers'] = [
...
...
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