-
Notifications
You must be signed in to change notification settings - Fork 6.5k
[CF1] dash SSO email domain callout #22105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryAdded a caution note regarding the global application of Cloudflare Dashboard SSO for email domains, clarifying that all users must authenticate via the specified identity provider.
Modified Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add |
@@ -35,6 +35,12 @@ Once your SSO domain is approved, a new **SSO App** application will appear unde | |||
- Every user with that email domain must be an employee in your organization. For example, university domains such as `@harvard.edu` are not allowed because they include student emails. | |||
- Your SSO domain can include multiple email domains. | |||
|
|||
:::caution | |||
|
|||
Enabling Cloudflare Dashboard SSO for an email domain (for example, `@mycompany.com`) will apply globally across all Cloudflare accounts where users log in with that domain. All users will be required to authenticate via the specified identity provider (IdP), including users on pre-existing Cloudflare accounts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kennyj42 if Access allows multiple IdPs on an account, would this technically be more correct if it was:
All users will be required to authenticate via the specified identity providers (IdPs), including users on pre-existing Cloudflare accounts.
plural?
This step only says "set up an IdP" https://developers.cloudflare.com/cloudflare-one/applications/configure-apps/dash-sso-apps/#1-set-up-an-idp but technically, they could have multiple. Let me know which wording you think is best.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
correct. all accounts for that domain will become sso'd
Preview URL: https://22402a38.preview.developers.cloudflare.com Files with changes (up to 15) |
Summary
PCX-16429
Screenshots (optional)
Documentation checklist