Repository navigation
docs: Okta SSO setup is self-service in the dashboard - #1027
Conversation
The Okta page told readers to email their Client ID, Client Secret and domains to NetBird support. SSO is now set up in Integrations > Single Sign-On > Connect Okta, where the wizard takes those values directly and then asks for domain ownership verification if needed. - Point the entry path at the Single Sign-On tab and the wizard's Get Started / Continue / Connect steps - Replace the email step with the form fields and the Verify Domain Ownership flow (TXT record, Verify Later, email fallback) - Replace the outdated SCIM-wizard screenshot with one of the Enter your Okta details form - Fix the app.netbird.io link and drop the Okta Verify reference Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@emrcbrn is attempting to deploy a commit to the NetBird GmbH Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
⛔ Files ignored due to path filters (2)
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe Okta SSO instructions now guide readers through the Single Sign-On wizard, credential entry, and domain ownership verification. They replace instructions to email credentials for manual enablement. ChangesOkta SSO guide
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~8 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to The guide now directs Okta administrators through dashboard-based SSO setup instead of emailing credentials. No specific mismatch or merge-blocking risk is established. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Warning Some tools did not complete. Review the errors below. 🔧 ESLint
src/pages/manage/team/idp-sync/okta-sync.mdxtypescript-eslint does not support TS 7.0. Oops! Something went wrong! :( ESLint: 9.39.5 Error: typescript-eslint does not support TS 7.0. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit reads the wizard with care, Comment |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Summary
The Okta page told readers to email their Okta Client ID, Client Secret and domains to NetBird support. That's no longer how it works. SSO is self-service: Integrations > Single Sign-On > Connect Okta opens a wizard that takes those values directly.
Changes
Single Sign-Ontab, not the Identity Provider Sync page. The button names match the wizard:Get Started →,Continue →,Connect.Connect, the dashboard can showVerify Domain Ownership. The page documents thenb-verification=TXT record,Verify Later, retrying fromSettings > Domains, and the email-from-the-domain fallback. The wording is conditional ("If your primary email domain isn't verified yet…"), matching the dashboard, which only opens the dialog when the domain isn't verified.Enter your Okta detailsform. Everything else is described in text.app.netbird.iolink was missing its scheme, and "log in using Okta Verify" becomes "log in with your Okta account".The
#configuring-sso-in-oktaheading is unchanged, because the dashboard's "Learn more" link points at it.Verification
main:src/modules/integrations/sso/okta/OktaSSOSetup.tsx,src/modules/integrations/sso/DomainVerificationModal.tsxandsrc/modules/integrations/sso/okta/OktaSSOSettings.tsx.npm run lint:mdxandnpm run buildpass. The page was also reviewed on the local dev server.Other SSO pages (Cognito, Zoho, Zitadel, Keycloak, Authentik, cidaas, Duo, IIJ) still say to email support. That's still correct: Okta is the only provider with a self-service card on the Single Sign-On tab.
🤖 Generated with Claude Code
Summary by CodeRabbit