Skip to content
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

Updating SSO migration #6838

Merged
merged 5 commits into from
Jan 28, 2025
Merged

Updating SSO migration #6838

merged 5 commits into from
Jan 28, 2025

Conversation

matthewshaver
Copy link
Contributor

@matthewshaver matthewshaver commented Jan 28, 2025

What are you changing in this pull request and why?

Updating the migration guide based on customer feedback

See https://www.notion.so/dbtlabs/SSO-Migration-updates-for-ST-18cbb38ebda780fe801aeaf9b773e478

Checklist

  • I have reviewed the Content style guide so my content adheres to these guidelines.
  • The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
  • I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
  • The content in this PR requires a dbt release note, so I added one to the release notes page.

🚀 Deployment available! Here are the direct links to the updated files:

@matthewshaver matthewshaver requested a review from a team as a code owner January 28, 2025 15:18
Copy link

vercel bot commented Jan 28, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
docs-getdbt-com ✅ Ready (Inspect) Visit Preview Jan 28, 2025 5:06pm

@github-actions github-actions bot added content Improvements or additions to content Docs team Authored by the Docs team @dbt Labs size: small This change will take 1 to 2 days to address labels Jan 28, 2025
There are two fields in these settings that you will need for the migration:
:::warning vanity urls

Don't use vanity URLs when configuring the SSO settings. You need to use the generic URL provided in the SSO settings for your environment. For example, if your vanity URL is `cloud.MY_COMPANY.getdbt.com`, configure `auth.cloud.getdbt.com` as `<YOUR_AUTH0_URI`>`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hiya @matthewshaver

It looks like there's an extra apostrophe here: <YOUR_AUTH0_URI>`.
I'm not sure which one needs removing - I don't want to mess up the doc.

Kind Regards
Natalie

Copy link
Contributor

@nataliefiann nataliefiann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hiya @matthewshaver

Thanks for creating this PR. I've approved this for you and left two non-blocking suggestions / questions.

Kind Regards
Natalie

@matthewshaver matthewshaver enabled auto-merge (squash) January 28, 2025 16:55
@matthewshaver matthewshaver merged commit 77b4edd into current Jan 28, 2025
8 checks passed
@matthewshaver matthewshaver deleted the sso-update branch January 28, 2025 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content Docs team Authored by the Docs team @dbt Labs size: small This change will take 1 to 2 days to address
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants