docs: document migrating existing accounts to SSO - #1134
Open
Anty0 wants to merge 2 commits into
Open
Conversation
Setting up SSO never converted accounts that already existed, and nothing in the docs said so. Neither the voluntary "Migrate to SSO" button nor the "Enforce SSO for Organization Users" switch was documented anywhere. Add a page covering both paths, what migration changes about an account (password and 2FA are deleted, the account becomes managed by the organization, the step cannot be undone), why the button may be missing, and the fact that personal access tokens and project API keys stop working for users who have not migrated once enforcement is on. Also rename the Authorization/Token URL rows in the getting started field table to match the labels the form actually uses.
✅ Deploy Preview for tolgee-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Every other SSO page opens with the notice directly under the title.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Enabling SSO does not convert accounts that already exist, and the docs never said so. Neither way of moving existing users onto SSO was documented anywhere:
Migrate to SSObutton onAccount securityEnforce SSO for Organization Usersswitch in the organization SSO settingsThe only existing hint was one sentence in the self-hosted setup page about SSO sign-ups being managed by their organization.
What this adds
A new page, Migrating Existing Users to SSO, placed in the SSO section right after Getting Started, covering:
Global SSO differs (migration does not bind the account to an organization), so that is called out separately.
Other changes
sso_getting_started,sso_server_setupandpassword_and_2fa, including a short2FA and SSOsubsection warning that migration destroys recovery codes.Authorization URL/Token URL; the form labels themAuthorization Endpoint/Token Endpoint.Verification
npm run buildpasses, so the new sidebar entry and every internal link resolve. Screenshots were taken against a locally running instance and use placeholder values (example.com,Acme Inc.).