You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the RFC7523 strategy, the audience is require to be the token endpoint url (code). Instead, I would like the audience matching strategy from the fosite config to be applied. My takeaway from reading the RFC is that the token url is suggested but the claim allows for flexibility https://datatracker.ietf.org/doc/html/rfc7523#section-3
Describe your ideal solution
If an audience matching strategy is set in the fosite config, use it in the RFC7523 strategy.
Workarounds or alternatives
I have not found a workaround
Version
0.46.1
Additional Context
If approved I'd be happy to raise a PR
The text was updated successfully, but these errors were encountered:
Preflight checklist
Ory Network Project
No response
Describe your problem
When using the RFC7523 strategy, the audience is require to be the token endpoint url (code). Instead, I would like the audience matching strategy from the fosite config to be applied. My takeaway from reading the RFC is that the token url is suggested but the claim allows for flexibility https://datatracker.ietf.org/doc/html/rfc7523#section-3
Describe your ideal solution
If an audience matching strategy is set in the fosite config, use it in the RFC7523 strategy.
Workarounds or alternatives
I have not found a workaround
Version
0.46.1
Additional Context
If approved I'd be happy to raise a PR
The text was updated successfully, but these errors were encountered: