quiet-window-70232
01/27/2023, 10:57 AMusername field. Currently setting username to session.access_token in OAuth2Consent respond. Also trying to enable oauth2.allowed_top_level_claims in my Ory Network OAuth2 Config. However claim gets set to ext object, instead of top level.
It seems like Ory Network has this configuration field mapped to the oauth2.session.allowed_top_level_claims , where as the Open Source project is looking at the oauth2.allowed_top_level_claims. Can you check?
Open Source: https://github.com/ory/hydra/blob/master/driver/config/provider.go#L91
Ory Network Config in ScreenShot:quiet-window-70232
01/27/2023, 10:58 AMquiet-window-70232
01/27/2023, 3:18 PMoauth2.allowed_top_level_claims is the correct path: https://www.ory.sh/docs/hydra/guides/jwt#adding-custom-claims-top-level-to-the-access-tokenquiet-window-70232
01/27/2023, 3:42 PMsetProject operation and its spec closed source? I can't find where this configuration schema is misconfigured 🤔high-optician-2097
high-optician-2097
high-optician-2097
ory patch oauth2-config --replace /oauth2/session/allowed_top_level_claims=["foo","bar"] --project abcdequiet-window-70232
01/27/2023, 7:16 PMoauth2/session/allowed_top_level_claims with the command you sent, or via update command. Both cases, I only get ext.username. Even though I can validate that oauth2.session.allowed_top_level_claims is set.
I think the problem is, Ory Hydra is using oauth2.allowed_top_level_claims whereas the Ory Cloud setProject is configured to use oauth2.session.allowed_top_level_claims.
So this configuration never works. The documentation also states that this variable should be under oauth2., not oauth2.session.
Where should I create an issue for this?high-optician-2097
quiet-window-70232
01/27/2023, 7:20 PMhigh-optician-2097
quiet-window-70232
01/27/2023, 7:45 PM