Authenticate API requests #102
Open
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
rishabhp58 force-pushed the authenticated-requests branch from 3edca70 to 9371554 Compare 
…o request headers for authenticating api requests within backstage Signed-off-by: Rishabh Patel <rpatel@fanatics.com> Signed-off-by: Rishabh Patel <rishabhpatel58@gmail.com>
rishabhp58 force-pushed the authenticated-requests branch from 9371554 to c269cfd Compare Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
With the addition of auth middleware for certain implementations the requests made through frontend plugins get rejected if they don't contain a valid token as a part of the request. The following changes incorporate the backstage identity api to fetch bearer tokens and attach them to request headers for authenticating api requests within backstage.