diff options
| author | hopegolden <44662040+hopegolden@users.noreply.github.com> | 2018-11-05 13:44:28 -0800 |
|---|---|---|
| committer | 无闻 <u@gogs.io> | 2018-11-05 16:44:28 -0500 |
| commit | 6a083e95611173df1ea2327c22b25780b61bfc29 (patch) | |
| tree | 09a597e0c98e948f24d527891fe69da85e311236 /pkg | |
| parent | 044d359a7eb1bd80eded2fc9af1e0807b209c6ee (diff) | |
ldap: grammar fix (#5493)
Diffstat (limited to 'pkg')
| -rw-r--r-- | pkg/auth/ldap/README.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/pkg/auth/ldap/README.md b/pkg/auth/ldap/README.md index b8c95b3b..bc357e96 100644 --- a/pkg/auth/ldap/README.md +++ b/pkg/auth/ldap/README.md @@ -11,7 +11,7 @@ LDAP via BindDN functions like most LDAP authentication systems. First, it queries the LDAP server using a Bind DN and searches for the user that is attempting to sign in. If the user is found, the module attempts to bind to the server using the user's supplied credentials. If this succeeds, the user has -been authenticated, and his account information is retrieved and passed to the +been authenticated, and their account information is retrieved and passed to the Gogs login infrastructure. LDAP simple authentication does not utilize a Bind DN. Instead, it binds @@ -20,7 +20,7 @@ succeeds and no filter rules out the user, the user is authenticated. LDAP via BindDN is recommended for most users. By using a Bind DN, the server can perform authorization by restricting which entries the Bind DN account can -read. Further, using a Bind DN with reduced permissions can reduce security risk +read. Furthermore, using a Bind DN with reduced permissions can reduce security risk in the face of application bugs. ## Usage |