-
Notifications
You must be signed in to change notification settings - Fork 295
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/Extension] Audit log entry for OBO token generation #3098
Comments
We need to better understand what compliance requirements look like around these new use cases. |
Cannot make progress on this item until [1] is resolved |
Resolving #3098, but removing triaged label from this issue to signal that requirements are still needed in its description. |
This seems to be coming from Extensions and not a standalone user request. @dagneyb if you have an opinion from extensions pov.
We can evolve this in future as we get more incremental user feedback around this. |
@RyanL1997 from what @setiah has added here, I think adding an audit category, and then adding another task for the documentation and what we have above should be all we need. What do you think? If you think so can you update this issue and the related issues? |
[Triage] Just following up @RyanL1997. Thank you! |
[Triage] Hi @RyanL1997, please add information for the exit criteria of this issue and then assign the triaged label. |
Hi @scrawfor99, I just added the exit criteria of this issue. |
Description
After the JwtVendor has generated an OBO token, it's essential that we link the audit log to track its usage, along with any specific information pertaining to this token.
Some of the information that should be traceable:
Exit Criteria
The text was updated successfully, but these errors were encountered: