Skip to content

Commit cd3337a

Browse files
Fix build errors... again
1 parent ceea79c commit cd3337a

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

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

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,28 +9,33 @@ If you experience issues with single sign-on (SSO), refer to the following solut
99
## Groups are not formatted correctly
1010

1111
#### Error message
12+
1213
When this issue occurs, the following error message is common:
1314
```bash
1415
sso error: Some of the groups assigned to the user are not formatted as '<organization name>:<team name>'. Directory groups will be ignored and user will be provisioned into the default organization and team.
1516
```
1617

1718
#### Possible causes
19+
1820
The following causes may create this issue:
1921
- Incorrect group name formatting in your identity provider (IdP): Docker requires groups to follow the format `<organization>:<team>`. If the groups assigned to a user do not follow this format, they will be ignored.
2022
- Non-matching groups between IdP and Docker organization: If a group in your IdP does not have a corresponding team in Docker, it will not be recognized, and the user will be placed in the default organization and team.
2123

2224
#### Affected environments
25+
2326
The following environments can be affected by this issue:
2427
- Docker single sign-on setup using IdPs such as Okta or Azure AD
2528
- Organizations using group-based role assignments in Docker
2629

2730
#### Steps to replicate
31+
2832
Use the following steps to replicate this issue:
2933
1. Attempt to sign in to Docker using SSO.
3034
2. The user is assigned groups in the IdP but does not get placed in the expected Docker team.
3135
3. Review Docker logs or IdP logs to find the error message.
3236

3337
#### Solution
38+
3439
The recommended solution is to update group names in your IdP:
3540
1. Go to your IdP's group management section.
3641
2. Check the groups assigned to the affected user.

0 commit comments

Comments
 (0)