Skip to content
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.

Sign up for GitHub

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

Jump to bottom

support RFC 8707 to request AT audience #841

Open
maarten-litmaath opened this issue Sep 7, 2024 · 5 comments
Open

support RFC 8707 to request AT audience #841

maarten-litmaath opened this issue Sep 7, 2024 · 5 comments

Comments

@maarten-litmaath
Copy link

Recent versions of oidc-agent by default use RFC 8707 to request access tokens with audiences, while for IAM the legacy method needs to keep being used, as described here:

https://github.com/indigo-dc/oidc-agent/releases/tag/v5.0.0

It would seem a good idea to let IAM support that RFC in addition, for the time being. This does not look urgent.
@federicaagostini
Copy link
Contributor

Same as #381.

@vokac vokac mentioned this issue Jan 6, 2025
Open
@panta-123
Copy link

Any update here ?

@federicaagostini
Copy link
Contributor

Hi, there is a work in progress PR #888. What's still missing there, is to save the requested resources in the original authorization request, such to allow for a narrower resource list appearing in the access token.

@rmiccoli rmiccoli linked a pull request Jan 30, 2025 that will close this issue
Add support for resource parameter #888
Closed
@panta-123
Copy link

@federicaagostini , Does this apply to client credential grant as well ?
Looking at RFC it mentions only authorization request, access token request using authorization_code grant and refresh_token grant.

@federicaagostini
Copy link
Contributor

Hi, yes we are implementing the ability to request for a resource parameter in all flows (also device code and token exchange). My guess is that the RFC reports examples about the more used flows in industry. It should behave quite similarly to the audience parameter, do you agree?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for resource parameter indigo-iam/iam
3 participants
@federicaagostini @maarten-litmaath @panta-123