Open
Conversation
Contributor
|
Currently, the code supports only a single valid API key, which creates an authentication issue since it cannot answer the question “Who is making the request?”. If we have multiple clients sending requests, there is no way to log which specific client made a request to the Policy Server, nor is there a way to revoke a specific key in case it is compromised. This leads to a second problem: the API key is stored in environment variables. If it gets leaked, rotating it would require modifying the application configuration directly. |
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
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.
enabled api key as optional env. If enabled, all requests should have in header x-api-key set