Bug report
Describe the bug
Zitadel sends roles in ID token using keys urn:zitadel:iam:org:project:<projectid>:roles and urn:zitadel:iam:org:project:roles. However, these keys are not present in session object returned from supabase.auth.getSession.
To Reproduce
- Create Zitadel project.
- Enable Asset Roles on Authentication in project settings.
- Create application(WEB/CODE) under project.
- Enable User roles inside ID Token in token settings.
- Add Zitadel as custom OIDC provider.
- Authenticate using
supabase.auth.signInWithOAuth and check session data using supabase.auth.getSession.
Expected behavior
Roles sent by Zitadel in ID token should be present in session data.
System information
- Self hosted Supabase
- supabase/gotrue:v2.188.1
Bug report
Describe the bug
Zitadel sends roles in ID token using keys
urn:zitadel:iam:org:project:<projectid>:rolesandurn:zitadel:iam:org:project:roles. However, these keys are not present in session object returned fromsupabase.auth.getSession.To Reproduce
supabase.auth.signInWithOAuthand check session data usingsupabase.auth.getSession.Expected behavior
Roles sent by Zitadel in ID token should be present in session data.
System information