diff options
author | Alex Jordan <alex@strugee.net> | 2015-11-16 02:01:26 -0800 |
---|---|---|
committer | Alex Jordan <alex@strugee.net> | 2015-11-16 16:50:05 -0800 |
commit | 3300db70ff53699732672824859186cd083623fa (patch) | |
tree | 98a8e79a3887ad710c8f09651ad5dc62e2598dcc /doc/integration/ldap.md | |
parent | 3777b233a35509c4ed13e145624370884468cbc2 (diff) | |
download | gitlab-ce-3300db70ff53699732672824859186cd083623fa.tar.gz |
Rewrite HTTP links to force TLS, where possible
Diffstat (limited to 'doc/integration/ldap.md')
-rw-r--r-- | doc/integration/ldap.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/integration/ldap.md b/doc/integration/ldap.md index 9b7d8fa3969..7e2920b8865 100644 --- a/doc/integration/ldap.md +++ b/doc/integration/ldap.md @@ -71,7 +71,7 @@ main: # 'main' is the GitLab 'provider ID' of this LDAP server # Filter LDAP users # - # Format: RFC 4515 http://tools.ietf.org/search/rfc4515 + # Format: RFC 4515 https://tools.ietf.org/search/rfc4515 # Ex. (employeeType=developer) # # Note: GitLab does not support omniauth-ldap's custom filter syntax. @@ -145,7 +145,7 @@ If multiple LDAP email attributes are present, e.g. `mail: foo@bar.com` and `ema ## Using an LDAP filter to limit access to your GitLab server If you want to limit all GitLab access to a subset of the LDAP users on your LDAP server you can set up an LDAP user filter. -The filter must comply with [RFC 4515](http://tools.ietf.org/search/rfc4515). +The filter must comply with [RFC 4515](https://tools.ietf.org/search/rfc4515). ```ruby # For omnibus packages; new LDAP server syntax |