Ory doesn't appear to follow standards for scope claims

[Gonkers]

Ory uses scp rather than the proper scope claim when returning JWTs. It appears that I am not the only one who ran into this issue. But it looks like someone contributed a fix some time ago and it was released as part of Hydra v2.2.0-rc.3.

I have been unable to find any documentation on how to use the scope claim in the ory docs. Can someone point me in the correct direction?

[Gonkers]

I have found this configuration spec and it mentions the new strategy for how ory returns scope claims. So that looked promising.

I attempted to patch the config with following command...

ory patch oauth2-config 00000000-0000-0000-0000-000000000000 --replace '/strategies/jwt/scope_claim="string"'

But the change seemed to be ignored.

I then attempted to save the full config, update the local file, then reapply it on the service.

ory get oauth2-config 00000000-0000-0000-0000-000000000000 --format yaml > oauth2-config.yaml

I updated the strategies section to the following...

strategies:
  access_token: jwt
  scope: wildcard
  jwt: 
    scope_claim: string

finally I updated the config with the command below

ory update oauth2-config 00000000-0000-0000-0000-000000000000 --file oauth2-config.yaml

This did not work either. I ran the ory get command again to find that my access_token property was updated, but the jwt sub section was gone.

Is ory network not updated to Hydra v2.2.0 ?

[aeneasr]

Hey, thank you for providing so much detail! It looks like we missed adding this variable to our config schema in Ory Network. So this is a bug on our end :)