-
Notifications
You must be signed in to change notification settings - Fork 85
feat (TUI): JWT Response for OAuth Token Introspection #6382
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
Comments
It is already done. See #3658 (comment) |
I changed this to track a feature request for the TUI. |
@devrimyatar please hold on. Not sure how it got missed but AS picks up signing algorithm from
Also supported algs has to be introduced by discovery endpoint. Re-opened - #3658 |
@yuriyz,
Please confirm which attributes from this schema definition or if any change required in config-api for this issue. |
@pujavs it's about For example these are missed in swagger:
|
Regenerated openapi spec to reflect new fields and pushed changes via PR 6566 |
This was implemented in #3658, but I'm not sure it was exposed in the TUI. For example, it could be in the
Encryption/Signing
section, or it could also be in theTokens
section.I dont' see any way to configure the signing and encryption for the introspection endpoint.

For example here is a screenshot of Forgerock:

The text was updated successfully, but these errors were encountered: