fix: avoid OIDC discovery on policy reload - #7
Merged
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
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.
Outcome\n\n- adopt policy-only OIDC reloads in memory without re-running discovery or provider construction\n- preserve full initialization for startup, initial enablement, provider switches, and identity-source changes\n- add regression coverage and publish v0.4.41 documentation/version gates\n\n## Validation\n\nThe branch security gate performs formatting/static checks, the full race-enabled Go suite, two byte-identical builds, SBOM generation, secret scanning, and vulnerability/VEX gates. Runtime acceptance will be repeated against the QA Authentik deployment before the Server patch is considered complete.