Repository navigation
Add waffle switch for enabling/disabling asymmetric auth - #1788
Merged
ryan-morosa merged 2 commits intoOct 30, 2026
Merged
Conversation
ryan-morosa
marked this pull request as ready for review
October 29, 2026 21:28
jimmyfagan
approved these changes
Oct 29, 2026
jimmyfagan
left a comment
Contributor
There was a problem hiding this comment.
Looks good! Let's touch base tomorrow about getting these recent waffle switches sorted out prior to the next deployment!
ryan-morosa
deleted the
ryan-morosa/add-waffle-switch-for-blocking-asymm-auth
branch
October 30, 2026 01:31
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.
JIRA Ticket:
N/A
What Does This PR Do?
This PR adds a waffle switch for controlling whether or not asymmetric auth can be allowed or disallowed. It's based upon the conversation from slack here.
What Should Reviewers Watch For?
If you're reviewing this PR, please check for these things in particular:
Validation
What Security Implications Does This PR Have?
Please indicate if this PR does any of the following:
security engineer's approval.
Any Migrations?
etc)