Skip to content

fix(auth): conditionally show unlinked member warning based on SSO requirement#115461

Open
sentry-junior[bot] wants to merge 1 commit into
masterfrom
fix/sso-unlinked-members-warning-message
Open

fix(auth): conditionally show unlinked member warning based on SSO requirement#115461
sentry-junior[bot] wants to merge 1 commit into
masterfrom
fix/sso-unlinked-members-warning-message

Conversation

@sentry-junior
Copy link
Copy Markdown
Contributor

@sentry-junior sentry-junior Bot commented May 13, 2026

Problem

When an SSO provider is configured but Require SSO is not enabled, the Auth Settings page shows this warning for unlinked members:

There are currently X member(s) who have not yet linked their account with <provider>. Until this is done they will be unable to access the organization.

This is misleading — when SSO is not required, unlinked members can still access the organization via email/password login at the generic auth page. They just can't use the SSO provider login flow.

Solution

  • Pass the require_link flag (derived from auth_provider.flags.allow_unlinked) to the template context
  • Conditionally show an accurate message depending on whether SSO is actually required:
    • Required: keep the existing warning — unlinked members truly cannot access the org
    • Not required: show a new message explaining they can still use email/password, but won't be able to log in via the SSO provider until they link their account

Changes

  • src/sentry/web/frontend/organization_auth_settings.py: added require_link to template context
  • src/sentry/templates/sentry/organization-auth-provider-settings.html: conditional warning message based on require_link

Closes https://github.com/getsentry/sentry/issues/XXXXX


PR created on behalf of @NickMeisenheimer

…quirement

When an SSO provider is configured but 'Require SSO' is not enabled,
the unlinked members warning incorrectly states that unlinked members
'will be unable to access the organization.' In reality, they can still
log in with email and password — they just can't use the SSO provider.

Pass the require_link flag to the template context and show an accurate
message depending on whether SSO is actually required:
- Required: keep the existing 'unable to access' warning
- Not required: explain they can still use email/password but can't use
  the SSO provider until linked
@sentry-junior sentry-junior Bot requested review from a team as code owners May 13, 2026 00:18
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label May 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants