blue-needle-37891
06/26/2023, 7:55 AMhttps://<our_custom_domain>/oauth2/sessions/logout?state=<STATE>&idToken=<ID_TOKEN>&post_logout_redirect_uri=<REDIRECT_URI>
.
However, we receive the following error message:
https://<our_custom_domain>/ui/error?error=invalid_request&error_description=The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed. Logout failed because query parameter post_logout_redirect_uri is not whitelisted as a post_logout_redirect_uri for the client.
Although REDIRECT_URI
is correctly registered as suggested in https://www.ory.sh/docs/hydra/debug#redirect-url-isnt-whitelisted, we’re still encountering this issue.
According to a forum post (https://community.ory.sh/t/how-to-use-post-logout-redirect-uris-param-to-logout-in-pkce-mode/), there should be a post_logout_redirect_uris
setting for each client, where valid post-logout redirect URIs can be added. However, I haven’t been able to find the procedure for doing this through the Ory Console or CLI.
I would greatly appreciate it if someone could guide me in the right direction. Thank you.blue-needle-37891
07/03/2023, 9:04 AMfast-lunch-54279
proud-plumber-24205
07/03/2023, 11:24 AMpost_logout_callback
field when creating the client.
I think the Ory Console does not have an option to set the post_logout_callback
, but the CLI does have such an option:
$ ory create oauth2-client -h
This command creates an OAuth 2.0 Client which can be used to perform various OAuth 2.0 Flows like
the Authorize Code, Implicit, Refresh flow. This command allows settings all fields defined in the OpenID Connect Dynamic Client Registration standard.
To encrypt an auto-generated OAuth2 Client Secret, use flags `--pgp-key`, `--pgp-key-url` or `--keybase` flag, for example:
ory create oauth2-client -n "my app" -g client_credentials -r token -a core,foobar --keybase keybase_username
Usage:
ory create oauth2-client [flags]
Aliases:
oauth2-client, client
Examples:
ory create oauth2-client -n "my app" -c <http://localhost/cb> -g authorization_code -r code -a core,foobar
Use the tool jq (or any other JSON tool) to get the OAuth2 Client ID and and Secret:
client=$(ory create oauth2-client \
--format json \
...)
echo $client
# Parse the JSON response using jq to get the client ID and client secret:
client_id=$(echo $client | jq -r '.client_id')
client_secret=$(echo $client | jq -r '.client_secret')
Flags:
--allowed-cors-origin strings The list of URLs allowed to make CORS requests. Requires CORS_ENABLED.
--audience strings The audience this client is allowed to request.
--backchannel-logout-callback string Client URL that will cause the client to log itself out when sent a Logout Token by Hydra.
--backchannel-logout-session-required Boolean flag specifying whether the client requires that a sid (session ID) Claim be included in the Logout Token to identify the client session with the OP when the backchannel-logout-callback is used. If omitted, the default value is false.
--client-uri string A URL string of a web page providing information about the client
--contact strings A list representing ways to contact people responsible for this client, typically email addresses.
--format string Set the output format. One of table, json, yaml, json-pretty, and jsonpath. (default "default")
--frontchannel-logout-callback string Client URL that will cause the client to log itself out when rendered in an iframe by Hydra.
--frontchannel-logout-session-required Boolean flag specifying whether the client requires that a sid (session ID) Claim be included in the Logout Token to identify the client session with the OP when the frontchannel-logout-callback is used. If omitted, the default value is false.
--grant-type strings A list of allowed grant types. (default [authorization_code])
-h, --help help for oauth2-client
--jwks-uri private_key_jwt Define the URL where the JSON Web Key Set should be fetched from when performing the private_key_jwt client authentication method.
--keybase string Keybase username for encrypting client secret.
--logo-uri string A URL string that references a logo for the client
--metadata string Metadata is an arbitrary JSON String of your choosing. (default "{}")
--name string The client's name.
--owner string The owner of this client, typically email addresses or a user ID.
--pgp-key string Base64 encoded PGP encryption key for encrypting client secret.
--pgp-key-url string PGP encryption key URL for encrypting client secret.
--policy-uri string A URL string that points to a human-readable privacy policy document that describes how the deployment organization collects, uses, retains, and discloses personal data.
--post-logout-callback strings List of allowed URLs to be redirected to after a logout.
--project string The project to use, either project ID or a (partial) slug.
-q, --quiet Be quiet with output printing.
--redirect-uri strings List of allowed OAuth2 Redirect URIs.
--request-object-signing-alg string Algorithm that must be used for signing Request Objects sent to the OP. (default "RS256")
--request-uri strings Array of request_uri values that are pre-registered by the RP for use at the OP.
--response-type strings A list of allowed response types. (default [code])
--scope strings The scope the client is allowed to request.
--secret string Provide the client's secret.
--sector-identifier-uri string URL using the https scheme to be used in calculating Pseudonymous Identifiers by the OP. The URL references a file with a single JSON array of redirect_uri values.
--subject-type public A identifier algorithm. Valid values are public and `pairwise`. (default "public")
--token-endpoint-auth-method client_secret_post Define which authentication method the client may use at the Token Endpoint. Valid values are client_secret_post, `client_secret_basic`, `private_key_jwt`, and `none`. (default "client_secret_basic")
--tos-uri string A URL string that points to a human-readable terms of service document for the client that describes a contractual relationship between the end-user and the client that the end-user accepts when authorizing the client.
Global Flags:
-c, --config string Path to the Ory Network configuration file.
-y, --yes Confirm all dialogs with yes.
blue-needle-37891
07/03/2023, 11:58 AMblue-needle-37891
07/06/2023, 9:56 AM