Skip to content

Commit b1a084e

Browse files
authored
remove 20h mention (#14313)
SSO session expiry length was changed from 20h to 7 days in 2023 getsentry/sentry#48596 getsentry/sentry@3af2fd9
1 parent 257dab6 commit b1a084e

File tree

1 file changed

+1
-1
lines changed
  • docs/organization/authentication/sso

1 file changed

+1
-1
lines changed

docs/organization/authentication/sso/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Every member who creates a new account via SSO will be given global organization
2424

2525
Our SSO implementation prioritizes security. We aggressively monitor linked accounts and will disable them if there's any reasonable sign that the account’s access may have been revoked. Generally this will be transparent to you, but if the provider is functioning in an unexpected way you may experience more frequent re-authorization requests.
2626

27-
Sessions last for [Django's default session length](https://docs.djangoproject.com/en/1.11/topics/http/sessions/#using-cookie-based-sessions), which is two weeks. For individual organizations with single sign-on, we expire organization access after one day (20 hours).
27+
Sessions last for [Django's default session length](https://docs.djangoproject.com/en/1.11/topics/http/sessions/#using-cookie-based-sessions), which is two weeks.
2828

2929
## Providers
3030

0 commit comments

Comments
 (0)