FI-3257: Use Custom Authorization Header Input in Invalid Token Test #81
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
Jammjammjamm
approved these changes
Oct 11, 2024
emichaud998
force-pushed
the
FI-3257_Use_Authorization_Headers_Invalid_Token_Test
branch
from
f062be1 to
1b42e81
Compare
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
This PR fixes GitHub Issue onc-healthit/onc-certification-g10-test-kit#572
Inferno allows test to specify authorization header for Token Introspection in the configuration input "HTTP Authorization Header for Introspection Request", but the invalid token test did not have the ability to use that custom header input. This PR adds the code to allow the invalid token test to use the custom authorization header input. This PR branch is branched off of #77, which is the PR that allows multi-line custom headers, so it includes those changes as well.
Testing Guidance
Run test kit locally and ensure any headers added to the custom authorization header input are added to the request in the invalid token test.