summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCynthia Ng <cng@gitlab.com>2019-06-13 18:35:49 +0000
committerCynthia Ng <cng@gitlab.com>2019-06-13 18:35:49 +0000
commit3e20e2186643d721c034149725d397300ac3005c (patch)
tree3ee575b129fe52c83aed85d2d202d9ace19d6da9
parentea9fcebfdf2aff296d3176ae57b909849d036c0b (diff)
downloadgitlab-ce-docs-sso-enforce-note.tar.gz
Add login session notedocs-sso-enforce-note
-rw-r--r--doc/user/group/saml_sso/index.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/user/group/saml_sso/index.md b/doc/user/group/saml_sso/index.md
index fcfd638f185..26893f7e31e 100644
--- a/doc/user/group/saml_sso/index.md
+++ b/doc/user/group/saml_sso/index.md
@@ -35,6 +35,8 @@ SSO enforcement was:
With this option enabled, users must use your group's GitLab single sign on URL to be added to the group or be added via SCIM. Users cannot be added manually, and may only access project/group resources via the UI by signing in through the SSO URL.
+However, users will not be prompted to log via SSO on each visit. GitLab will check whether a user has authenticated through the SSO link, and will only prompt the user to login via SSO if it has been longer than 7 days.
+
We intend to add a similar SSO requirement for [Git and API activity](https://gitlab.com/gitlab-org/gitlab-ee/issues/9152) in the future.
### NameID