OidcClaims

Who an identity provider says signed in.

Use what your sign-in gets after a person signs in through a provider such as Google. sub identifies them for good, and email can change. For a token's general claims, use JwtClaims.

Shape

Write every field when you build one, and give a field that isn't required as none.

Example

OidcClaims {    sub: "248289761001"    name: "Jane Doe"    given_name: none    family_name: none    preferred_username: none    email: none    email_verified: none    phone_number: none    phone_number_verified: none    picture: none}

Good to know

• == tells you whether two are the same. < and list.sort_by don't take it, so sort by one of its parts instead.

In JSON

An object of its parts, in a request, a response or json.write:

{"sub":"248289761001","name":"Jane Doe","given_name":"Jane","family_name":"Doe","preferred_username":"j.doe","email":"janedoe@example.com","email_verified":true,"picture":"https://example.com/janedoe/me.jpg"}{"sub":"248289761002","email":"j.doe@example.org","email_verified":false}{"sub":"248289761003"}

When you read one, a field that isn't required may be left out, or sent as null.

Details