[codex] Improve OIDC auth UI and context flow#14
Merged
Conversation
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
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.
Summary
Why
The OIDC provider login and signup screens did not clearly communicate which client application was requesting authentication before the user authenticated. This made the flow harder to trust and less aligned with the post-login consent step.
Impact
Users now see validated client and permission context earlier in the flow, password-only deployments land directly on the password form, and auth forms have stronger accessibility semantics across supported languages.
Validation
git diff --cached --checkpnpm biome check .pnpm buildpnpm test 2>&1 | Select-Object -Last 200Note: Windows did not have
tail, so the documentedtail -200test summary command was run with PowerShell'sSelect-Object -Last 200equivalent. Full tests exited successfully; Playwright reported three Firefox account-selection cases as flaky after retry, then passed.