feat(reverse-proxy): implement user blacklist functionality#1796
Merged
Conversation
Assisted-By: Cursor <cursoragent@cursor.com> Signed-off-by: Mayur Deshmukh <deshmukhmayur@outlook.com>
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
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.
Explain the feature/fix
Added a user blacklist feature to the reverse proxy service, allowing the service to block requests from specified users based on identifiers such as uid, email, or rhatUUID. This includes the addition of a new environment variable
BLACKLIST_FILE_PATHto specify the path to the blacklist file, which is loaded at startup. Updated middleware to check against the blacklist and return a 403 status for blocked users. Documentation in README.md has been updated to reflect these changes, and example blacklist file provided.blacklistBearerandblacklistOidcmiddleware for handling blacklist checks.Assisted-By: Cursor cursoragent@cursor.com
Does this PR introduce a breaking change
No.
Screenshots
N/A
Ready-for-merge Checklist