Giving an optional attribute to customize authorization header #146
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
Bumbleblo
changed the title
possibility to use a custom header for authorization in any Backstage instance. Signed-off-by: Felipe Borges <[email protected]>
Bumbleblo
force-pushed
the
feat/custom-backstage-authorization
branch
from
8da4492 to
3e2d0d8
Compare
samstarling
reviewed
Nov 3, 2024
Co-authored-by: Sam Starling <[email protected]>
Merged
samstarling
added a commit
that referenced
this pull request
Nov 4, 2024
2.4.3 includes the ability to specify an alternative name for your authorization header (#146).
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.
Make possible to use custom Headers values for authorization