Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

image.png

Despite configuring `phone` in the allowed OAuth scopes of an OAuth Client in the dashboard (see attached screenshot), and requesting it in Authorization Requests, both the ID Token and user profile return OpenID Standard Claims without a `phone_number` value.

I've tried configuring Identity Schemas with a trait of both `phone` and `phone_number` on the premise that the former is referenced in Ory documentation and the latter is the OpenID Connect naming convention, but neither worked.

I've checked GitHub in the Hydra repo for issues relating to this and gone through Ory docs, but I can't seem to find any way of getting Standard Claims to return to the OAuth client with a `phone_number`

The spec defines Standard Claims should contain `phone_number` and `phone_number_verified`: <https://openid.net/specs/openid-connect-basic-1_0.html#StandardClaims>

The spec also defines that the scope `phone` should be used to get access to this info: <https://openid.net/specs/openid-connect-basic-1_0.html#Scopes>
&gt; OPTIONAL. This scope value requests access to the phone_number and phone_number_verified Claims.
