sparse-father-97864
10/07/2024, 2:47 PMbrief-egg-61061
10/07/2024, 2:47 PMbrief-egg-61061
10/07/2024, 2:47 PM/.well-known/jwks.json
endpoint in your OAuth2 configuration, you need to use the ory patch oauth2-config
command. Here's an example of how to do it: bash ory patch oauth2-config --project <project-id> --workspace <workspace-id> \ --add '/webfinger/jwks/broadcast_keys/-="custom_keyset"'
In this command, replace <project-id>
and <workspace-id>
with your project's ID and workspace ID, respectively. "custom_keyset"
should be replaced with the name of your custom keyset. Before you can add a custom keyset, you need to create it. For more information on how to create a custom keyset, you can refer to the ory create jwk
command in the Ory documentation. Please note that the /.well-known/jwks.json
file is a standard endpoint that contains the public keys for verifying ID tokens and JWT access tokens. Ory OAuth2 and OpenID Connect expose this endpoint by default for each Ory Network project. Source: [Ory Documentation](https://www.ory.sh/docs/hydra/jwks#the-role-of-well-knownjwksjson)