Actions V2 PreAccessToken and requested scopes
I would like to use the actions v2 to add some claims to a jwt. Does the payload that the webhook receives contains the requested scope?
AHi @Matheus Zaniolo, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
AAnswer
---
I wasn't able to find a direct answer about whether the Actions v2 webhook payload for
preaccesstoken includes the requested scopes. Here are some relevant sources:- Migrate from Actions v1 to v2 (1) : Describes using the
preaccesstokenfunction to add claims to JWT access tokens, but does not detail the exact payload structure or whether scopes are included. - OAuth / Onboard User with additional Meta-Data (2) : Mentions that Actions v1 can access scopes via
request.oidc.scopes[], but notes that "Actions v2 will change this to be more easy" — suggesting the payload structure differs.
A
To learn more, see the sources I considered:
[1] Migrate from Actions v1 to v2
[2] OAuth / Onboard User with additional Meta-Data
To learn more, see the sources I considered:
[1] Migrate from Actions v1 to v2
[2] OAuth / Onboard User with additional Meta-Data
A
A
Rhey @Matheus Zaniolo I did not understand what are you trying to achieve, could you please tell me more on what are you trying to do?. Its descibed how claims are added when you try to set it here and here is the body of preAccesstoken
M@Rajat , I would like to add claims to the token based on the requested OIDC scopes. It seems that this was possible in actions v1 because we have access there to the requested scopes. Do we have a way to know the requested scopes in actions V2?