-
Notifications
You must be signed in to change notification settings - Fork 590
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
mt-broker-filter: Allow only requests from Subscriptions OIDC ID #7989
Comments
I would like to work on this |
/assign |
Hey @ayushrakesh, |
@creydr : got caught up in some other work, let @ayushrakesh : proceed with the changes |
Hello @ayushrakesh, are there anything I can help you with regarding this issue? |
Hello @ayushrakesh are you still planning to work on the issue? |
I can work on this if @ayushrakesh is not working on this |
@EraKin575 Sorry for delay, you can work on that. |
/assign |
Are there anything I could help you with? @EraKin575 If you're still working on this issue, please let me know within the next 24 hours. We understand that plans and priorities can change, and if you're no longer able to continue with this task, that's completely okay! In case I don't hear back from you in the next 24 hours, I'll unassign the issue from you. Of course, if you'd like to continue working on it later, you can always reassign it to yourself if it is still available. |
Sorry,for the delay. I am still working on this issue and will raise a PR ASAP |
sorry, this took a while |
We need to verify in the mt-broker-filter, that an request comes only from the Subscriptions OIDC is (
.status.auth.serviceAccountName
). Therefor we should do the following in the mt-broker-filter handler:.status.auth.serviceAccountName
).403
status codePrerequisites:
Additional context:
Additional hints for new contributors before starting with this issue:
Draft
status, the issue is subject to change and thus should not be started to be worked on/assign
). Please be aware that we might unassign you, if we don't see any progress from your side to give other contributors also a chance to work on this issue.The text was updated successfully, but these errors were encountered: