Repository navigation
Docs: provider-only sign-in mode (enterprise single sign-on) - #910
Merged
Merged
Conversation
KrzysztofPajak
force-pushed
the
feature/oidc-provider-only-plugin
branch
from
October 14, 2026 10:39
9752e24 to
ac817cc
Compare
KrzysztofPajak
force-pushed
the
feature/oidc-provider-only-guide-e2e
branch
from
October 14, 2026 10:39
b334b66 to
177c02b
Compare
KrzysztofPajak
force-pushed
the
feature/oidc-provider-only-plugin
branch
from
October 14, 2026 10:54
ac817cc to
e7d6340
Compare
KrzysztofPajak
force-pushed
the
feature/oidc-provider-only-guide-e2e
branch
from
October 14, 2026 10:55
177c02b to
ef89f82
Compare
KrzysztofPajak
force-pushed
the
feature/oidc-provider-only-plugin
branch
from
October 14, 2026 14:30
e7d6340 to
7d7bd4b
Compare
KrzysztofPajak
force-pushed
the
feature/oidc-provider-only-guide-e2e
branch
from
October 14, 2026 14:30
ef89f82 to
6d7a8d5
Compare
KrzysztofPajak
force-pushed
the
feature/oidc-provider-only-plugin
branch
from
October 14, 2026 16:15
7d7bd4b to
efe1582
Compare
KrzysztofPajak
force-pushed
the
feature/oidc-provider-only-guide-e2e
branch
from
October 14, 2026 16:15
6d7a8d5 to
1d35418
Compare
…the switch, Access control list tab, first access token after a browser sign-in, re-linking a user recreated at the provider, token and password-lifetime behaviour
…esses in profile sync; cross-site sign-out stays local
…bled admits existing accounts only
KrzysztofPajak
force-pushed
the
feature/oidc-provider-only-guide-e2e
branch
from
October 14, 2026 16:26
1d35418 to
a506e70
Compare
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.
Resolves no public issue
Type: feature
Issue
The provider-only sign-in mode (previous three pull requests in this stack) needs setup and operating guidance: what changes for customers and staff, break-glass accounts, guest browsing, provider post-logout settings and troubleshooting.
Fourth of four stacked pull requests (core → web → plugin → guide); based on the plugin branch.
Solution
New section 13 "Provider-only sign-in (enterprise single sign-on)" in
docs/oidc-resource-server.md: configuration (SignInMode,BreakGlassAccounts), what changes on each surface, break-glass accounts (two-factor before the switch,/admin/login?password=1, log warnings), guest browsing through the Guests group's Access control list, first sign-in and account linking, profile sync, sign-out and the post-logout redirect URI for Keycloak and Zitadel (including what each provider shows), access tokens and API clients, misconfiguration behaviour, switching back toMixed, troubleshooting (re-linking a user recreated at the provider). Two earlier lines in sections 11 and 12 are updated to match.Breaking changes
None (documentation only).
Testing
Followed end to end on a test installation with Keycloak 26.8 and Zitadel v4.19: storefront and panel redirects, registration through the provider, staff linked by verified e-mail, password and API refusals, break-glass sign-in, closed catalog for guests, inactive method notices, profile sync, sign-out at the provider.