mirror of https://github.com/docker/docs.git
security: update security faq, add sso faq (#22195)
## Description - Original security general FAQ was incorrect. IAM team confirmed that we do not currently support IdP default timeouts, and we should communicate this. - Updated existing FAQ - Added new FAQ to SSO FAQs ## Related issues or tickets - [ENGDOCS-2475](https://docker.atlassian.net/browse/ENGDOCS-2475) ## Reviews - [ ] Editorial review [ENGDOCS-2475]: https://docker.atlassian.net/browse/ENGDOCS-2475?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
This commit is contained in:
parent
592b28729b
commit
eec54cf457
|
@ -31,11 +31,13 @@ You can configure this through SSO using your IdP. Check with your IdP if they s
|
|||
|
||||
### How are sessions managed and do they expire?
|
||||
|
||||
Docker Desktop uses tokens to manage sessions after a user signs in. Docker Desktop signs you out after 90 days, or 30 days of inactivity.
|
||||
Docker uses tokens to manage sessions after a user signs in:
|
||||
|
||||
In Docker Hub, you need to re-authenticate after 24 hours. If users are authenticating using SSO, the default session timeout for the IdP is respected.
|
||||
- Docker Desktop signs you out after 90 days, or 30 days of inactivity.
|
||||
- Docker Hub and Docker Home sign you out after 24 hours.
|
||||
|
||||
Custom settings per organization for sessions aren't supported.
|
||||
Custom settings per organization for sessions aren't supported. Currently,
|
||||
Docker does not support your IdP's default session timeout for SSO users.
|
||||
|
||||
### How does Docker attribute downloads to us and what data is used to classify or verify the user is part of our organization?
|
||||
|
||||
|
|
|
@ -61,4 +61,14 @@ securely](/security/for-admins/provisioning/group-mapping/#use-group-mapping-wit
|
|||
|
||||
### Are there any firewall rules required for SSO configuration?
|
||||
|
||||
No. There are no specific firewall rules required for configuring SSO, as long as the domain `login.docker.com` is accessible. This domain is commonly accessible by default. However, in rare cases, some organizations may have firewall restrictions in place that block this domain. If you encounter issues during SSO setup, ensure that `login.docker.com` is allowed in your network's firewall settings.
|
||||
No. There are no specific firewall rules required for configuring SSO, as long as the domain `login.docker.com` is accessible. This domain is commonly accessible by default. However, in rare cases, some organizations may have firewall restrictions in place that block this domain. If you encounter issues during SSO setup, ensure that `login.docker.com` is allowed in your network's firewall settings.
|
||||
|
||||
### Does Docker use my IdP's default session timeout?
|
||||
|
||||
No. Currently, Docker does not support your IdP's default session timeout for
|
||||
SSO users.
|
||||
|
||||
Docker's default user session timeouts are as follows:
|
||||
|
||||
- Docker Desktop signs you out after 90 days, or 30 days of inactivity.
|
||||
- Docker Hub and Docker Home sign you out after 24 hours.
|
Loading…
Reference in New Issue