feat: assertion header is now configurable #45
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
DanielRailean
force-pushed
the
feat/auth-header-used-for-auth-is-now-configurable
branch
from
bab8482 to
c0c3be1
Compare
hafstroem
approved these changes
Oct 23, 2025
DanielRailean
deleted the
feat/auth-header-used-for-auth-is-now-configurable
branch
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.
About the PR
the value of the
'authorization'header has been used, until now, to receive temporary credentials from AWS STS.adding the option to select another header to be used for that, if needed.
account_idparameter can now be used as an alternative toaws_assume_role_arnChangelog
Other