-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Handle the edge cases of On-behalf-of Authentication #2891
Comments
[Triage] Thanks for filing the issue. |
Capturing comment from the pull request, [comment]
|
This issue was closed without any finding or description of the expectations, reopening. |
Transfer the conversation here (comment1, comment2). Hi @peternied, I can re-edit the issue if we choose to refactor the logic into a public field. But still I think as we mentioned in the standup before, the main goal of this original issue is having the functionality of block these 2 endpoint, which has been implemented. But I agree that we can keep using this issue for capture the follow-up work. |
The work to create a util class isn't critical path, lets organically do this work or not. |
Problem
Since the OBO Token can perform on behalf of another user, it is necessary for us to frame the usages of this token.
Goal for closing this issue
**Implemented functionalities **
Follow up work of refactoring
Reference
[1] : https://github.com/opensearch-project/security/pull/3179/files/b31555926c59aafe9a310d64918002b91d51c676#diff-0550f691677d70fb9da2b6d5baf7d342bc670e0618a8598a259117818cb66f86R230
[2] : #3179 (comment)
The text was updated successfully, but these errors were encountered: