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
d753b128
Commit
d753b128
authored
Nov 04, 2019
by
Horatiu Eugen Vlad
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add documentation for sign-in application setting
parent
8725f0ed
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
62 additions
and
0 deletions
+62
-0
changelogs/unreleased/35547-add-documentation-for-sign-in-application-setting.yml
...547-add-documentation-for-sign-in-application-setting.yml
+5
-0
doc/user/admin_area/settings/img/two_factor_grace_period.png
doc/user/admin_area/settings/img/two_factor_grace_period.png
+0
-0
doc/user/admin_area/settings/index.md
doc/user/admin_area/settings/index.md
+1
-0
doc/user/admin_area/settings/sign_in_restrictions.md
doc/user/admin_area/settings/sign_in_restrictions.md
+56
-0
No files found.
changelogs/unreleased/35547-add-documentation-for-sign-in-application-setting.yml
0 → 100644
View file @
d753b128
---
title
:
Add documentation for sign-in application setting
merge_request
:
19561
author
:
Horatiu Eugen Vlad
type
:
added
doc/user/admin_area/settings/img/two_factor_grace_period.png
0 → 100644
View file @
d753b128
17.2 KB
doc/user/admin_area/settings/index.md
View file @
d753b128
...
...
@@ -14,6 +14,7 @@ include:
-
[
Continuous Integration and Deployment
](
continuous_integration.md
)
-
[
Email
](
email.md
)
-
[
Sign up restrictions
](
sign_up_restrictions.md
)
-
[
Sign in restrictions
](
sign_in_restrictions.md
)
-
[
Terms
](
terms.md
)
-
[
Third party offers
](
third_party_offers.md
)
-
[
Usage statistics
](
usage_statistics.md
)
...
...
doc/user/admin_area/settings/sign_in_restrictions.md
0 → 100644
View file @
d753b128
---
type
:
reference
---
# Sign-in restrictions **(CORE ONLY)**
You can use sign-in restrictions to limit the authentication with password
for web interface and Git over HTTP(S), two-factor authentication enforcing, as well as
as configuring the home page URL and after sign-out path.
## Password authentication enabled
You can restrict the password authentication for web interface and Git over HTTP(S):
-
**Web interface**
: When this feature is disabled, an
[
external authentication provider
](
../../../administration/auth/README.md
)
must be used.
-
**Git over HTTP(S)**
: When this feature is disabled, a
[
Personal Access Token
](
../../profile/personal_access_tokens.md
)
must be used to authenticate.
## Two-factor authentication
When this feature enabled, all users will have to use the
[
two-factor authentication
](
../../profile/account/two_factor_authentication.md
)
.
Once the two-factor authentication is configured as mandatory, the users will be allowed
to skip forced configuration of two-factor authentication for the configurable grace
period in hours.
![
Two-factor grace period
](
img/two_factor_grace_period.png
)
## Sign-in information
All users that are not logged-in will be redirected to the page represented by the configured
"Home page URL" if value is not empty.
All users will be redirect to the page represented by the configured "After sign out path"
after sign out if value is not empty.
If a "Sign in text" in Markdown format is provided, then every user will be presented with
this message after logging-in.
## Settings
To access this feature:
1.
Navigate to the
**Settings > General**
in the Admin area.
1.
Expand the
**Sign-in restrictions**
section.
<!-- ## Troubleshooting
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
one might have when setting this up, or when something is changed, or on upgrading, it's
important to describe those, too. Think of things that may go wrong and include them here.
This is important to minimize requests for support, and to avoid doc comments with
questions that you know someone might ask.
Each scenario can be a third-level heading, e.g.
`### Getting error message X`
.
If you have none to add when creating a doc, leave this section in place
but commented out to help encourage others to add to it in the future. -->
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