Skip to content

Commit 935fdee

Browse files
remove troubleshooting section
1 parent 0f23607 commit 935fdee

File tree

1 file changed

+0
-23
lines changed

1 file changed

+0
-23
lines changed

content/manuals/enterprise/troubleshoot/troubleshoot-sso.md

Lines changed: 0 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -114,29 +114,6 @@ If you have SCIM enabled, troubleshoot your SCIM connection using the following
114114
1. Ensure that the attributes being synced from your IdP match Docker's [supported attributes](/manuals/enterprise/security/provisioning/scim.md#supported-attributes) for SCIM.
115115
1. Test user provisioning by trying to provision a test user through your IdP and verify if they appear in Docker.
116116

117-
## IdP-initiated sign in is not enabled for connection
118-
119-
### Error message
120-
121-
When this issue occurs, the following error message is common:
122-
```text
123-
IdP-Initiated sign in is not enabled for connection '$ssoConnection'.
124-
```
125-
126-
### Causes
127-
128-
Docker does not support an IdP-initiated SAML flow. This error occurs when a user attempts to authenticate from your IdP, such as using the Docker SSO app tile on the sign in page.
129-
130-
### Solutions
131-
132-
**Authenticate from Docker apps**
133-
134-
The user must initiate authentication from Docker applications (Hub, Desktop, etc). The user needs to enter their email address in a Docker app and they will get redirected to the configured SSO IdP for their domain.
135-
136-
**Hide the Docker SSO app**
137-
138-
You can hide the Docker SSO app from users in your IdP. This prevents users from attempting to start authentication from the IdP dashboard. You must hide and configure this in your IdP.
139-
140117
## Not enough seats in organization
141118

142119
### Error message

0 commit comments

Comments
 (0)