Prevent TrnMatchPolicy and TrnRequirementType from being overriden #741
Conversation
This file contains 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
MrKevJoy
approved these changes
Oct 17, 2023
gunndabad
force-pushed
the
prevent-trn-configuration-from-overrides
branch
from
2002749 to
f89b572
Compare
MrKevJoy
approved these changes
Oct 17, 2023
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.
We allow the client's configured
TrnMatchPolicyandTrnRequirementTypeto be overridden by query parameters on the authorization request for testing purposes but we shouldn't allow it in production for 'real' clients. This change adds guards to those overrides so that they're only allowed for thetestclient(I felt making it configurable per-service was overkill here).