Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…ts in their respective home directories
…ce it contained two topics; moved domain management into provision since sso has its own instructions in setup
|
/review |
|
❌ PR Review Failed — The review agent encountered an error and could not complete the review. View logs. |
| aliases: | ||
| - /security/for-admins/single-sign-on/troubleshoot/ | ||
| - /security/troubleshoot/troubleshoot-sso/ |
There was a problem hiding this comment.
let's add a redirect for /enterprise/troubleshoot/troubleshoot-sso/
There was a problem hiding this comment.
i've been fighting for my life against these redirects lmao. thank you!
| > [!NOTE] | ||
| > | ||
| > SCIM only manages users provisioned through your identity provider after | ||
| > SCIM is enabled. It cannot remove users who were manually added to your Docker | ||
| > organization before SCIM was set up. | ||
| > | ||
| > To remove those users, delete them manually from your Docker organization. | ||
| > For more information, see | ||
| > [Manage organization members](/manuals/admin/organization/members.md). |
There was a problem hiding this comment.
question: I am not really familiar with SCIM at all, but, does this also apply if you (for whatever reason) manually add a user to an organization (they are not provisioned through SCIM). Or only if they were manually added "before SCIM was set up"?
| > [!NOTE] | |
| > | |
| > SCIM only manages users provisioned through your identity provider after | |
| > SCIM is enabled. It cannot remove users who were manually added to your Docker | |
| > organization before SCIM was set up. | |
| > | |
| > To remove those users, delete them manually from your Docker organization. | |
| > For more information, see | |
| > [Manage organization members](/manuals/admin/organization/members.md). | |
| > [!NOTE] | |
| > | |
| > SCIM only manages users provisioned through your identity provider. | |
| > It cannot remove users who were manually added to your Docker organization. | |
| > | |
| > To remove manually added users, delete them manually from your Docker | |
| > organization. For more information, see | |
| > [Manage organization members](/manuals/admin/organization/members.md). |
There was a problem hiding this comment.
Good question. Do you mean users who are manually added after some method of provisioning is enabled in an org (auto/jit/scim)? Let me loop into @madisonsilva for a for sure answer -- i don't want to make assumptions, since the differences between the 3 provisioning methods are a bit subtle.
|
/review |
![docker-agent[bot]](https://avatars.githubusercontent.com/in/2787757?s=60&v=4){kind=small}
| --- | ||
| title: Troubleshoot single sign-on | ||
| linkTitle: Troubleshoot SSO | ||
| linkTitle: Troubleshoot |
There was a problem hiding this comment.
Missing redirect for moved page
This file is being moved from content/manuals/enterprise/troubleshoot/troubleshoot-sso.md to content/manuals/enterprise/security/single-sign-on/FAQs/troubleshoot-sso.md.
The old URL was /enterprise/troubleshoot/troubleshoot-sso/ (after Hugo strips the /manuals prefix).
The new URL is /enterprise/security/single-sign-on/faqs/troubleshoot-sso/.
The aliases section currently has:
/security/for-admins/single-sign-on/troubleshoot//security/troubleshoot/troubleshoot-sso/
But it's missing an alias for the old path /enterprise/troubleshoot/troubleshoot-sso/. This will cause broken links for anyone who bookmarked or linked to the old URL.
Fix: Add /enterprise/troubleshoot/troubleshoot-sso/ to the aliases array:
aliases:
- /security/for-admins/single-sign-on/troubleshoot/
- /security/troubleshoot/troubleshoot-sso/
- /enterprise/troubleshoot/troubleshoot-sso/2 participants
Updating Provision section, part of freshness updates. Will add details later. 🖖