Skip to content

Document login client ID setting for OAuth invite flow#4940

Open
shannonbradshaw wants to merge 1 commit intomainfrom
claude/oauth-login-client-id
Open

Document login client ID setting for OAuth invite flow#4940
shannonbradshaw wants to merge 1 commit intomainfrom
claude/oauth-login-client-id

Conversation

@shannonbradshaw
Copy link
Copy Markdown
Collaborator

@shannonbradshaw shannonbradshaw commented Apr 16, 2026

Source changes

  • viamrobotics/app#11652 (APP-15958): Added a Login client ID field to the organization settings white-labeling page. The field designates which registered OAuth app is used for the login and invite flow.
  • Backend behavior change: previously, any registered OAuth app would be used automatically as the FusionAuth login client (the first one in the ClientIDs array). Now, LoginClientID must be set explicitly; otherwise invite links fall back to Viam's default login screen.
  • Invite flow branding: when a user opens an organization invite link, the organization's logo URL is now passed to the FusionAuth login screen as a logo_url query parameter.

Docs changes

  • docs/organization/oauth.md: Added a new ## Designate a login client ID section after "Set up auth app" covering:
    • The UI navigation path (organization dropdown → Settings and invites → White Labeling → Login client ID).
    • The validation rules (client ID must match a registered OAuth app; the app must include the invite redirect URI).
    • The effect on invite flow behavior (branded login screen with organization logo when set, Viam default login when empty).

How I found these

  • Xref lookup: no direct xref match for LoginClientID; the OAuth setup flow lives in docs/organization/oauth.md.
  • Grep matches: LoginClientID and login client ID found zero matches in docs; FusionAuth matched 4 files, only oauth.md is about OAuth setup.
  • Searched ClientIDs, client_ids, OAuthLoginClientID in docs (zero matches).
  • Verified the field label in app/ui/src/routes/(auth-required)/organization/[org_id]/settings/white-labeling.svelte reads Login client ID under the White Labeling heading.

Generated by daily docs change agent

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 16, 2026

Deploy Preview for viam-docs ready!

Name Link
🔨 Latest commit d7e0a3a
🔍 Latest deploy log https://app.netlify.com/projects/viam-docs/deploys/69e5effd7fa91a000847bebd
😎 Deploy Preview https://deploy-preview-4940--viam-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 40 (no change from production)
Accessibility: 99 (no change from production)
Best Practices: 83 (no change from production)
SEO: 89 (no change from production)
PWA: 60 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Base automatically changed from new-docs-site to main April 17, 2026 16:24
App PR viamrobotics/app#11652 added a Login client ID field to organization
settings that designates which OAuth app is used for the login and invite
flow. The previous behavior of automatically using the first registered
OAuth app was removed. Invite links now show the organization's logo on the
branded login screen.

Add a new "Designate a login client ID" section to the OAuth setup guide
covering the UI navigation, validation requirements, and the resulting
invite flow behavior.
@shannonbradshaw shannonbradshaw force-pushed the claude/oauth-login-client-id branch from 382f389 to d7e0a3a Compare April 20, 2026 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants