I'm sorry for the inconvenience you're experiencing. The error message you're seeing is typically due to a mismatch between the

redirect_uri

parameter in your request and the pre-registered redirect URIs in your OAuth 2.0 Client's configuration. Unfortunately, based on the provided knowledge sources, there isn't a direct way to bypass this issue by passing in credentials differently. The

redirect_uri

is a crucial part of the OAuth 2.0 flow, and it needs to be correctly configured for the authentication process to work. Here are a few steps you can take to troubleshoot this issue: 1. Ensure the

redirect_uri

matches the authorized redirect URI: The

redirect_uri

query parameter in the URL should match the authorized redirect URI added to the social sign-in provider. If there's a mismatch, you'll need to correct it. [Source](https://www.ory.sh/docs/troubleshooting/troubleshooting-social-sign-in) 2. Check your OAuth 2.0 Client's configuration: You can use the

ory get oauth2-client {client.id}

command to check your client's configuration. Make sure the

redirect_uris

field includes the correct redirect URI. [Source](https://www.ory.sh/docs/hydra/debug#refresh-token-flow-fails) 3. Use a custom domain: If you're using

<http://oryapis.com|oryapis.com>

as your redirect URI domain and it's not working, you might need to use a custom domain instead. You can add your custom domain to the

redirect_uri

query parameter by adjusting your project's

base_redirect_uri

configuration. [Source](https://www.ory.sh/docs/troubleshooting/troubleshooting-social-sign-in) If you're still having trouble after trying these steps, I recommend referring to the [Ory documentation](https://www.ory.sh/docs/) for more detailed troubleshooting information.

The

redirect_uri

you provided seems to be URL-encoded and points to

<http://localhost:36209/>

. This URI should be one of the pre-registered redirect URIs in your OAuth 2.0 Client's configuration. Here are the steps to ensure that your

redirect_uri

is correctly configured: 1. Check your OAuth 2.0 Client's configuration: Use the

ory get oauth2-client {client.id}

command to check your client's configuration. Make sure the

redirect_uris

field includes

<http://localhost:36209/>

. [Source](https://www.ory.sh/docs/hydra/debug#refresh-token-flow-fails) 2. Update your OAuth 2.0 Client's configuration if necessary: If

<http://localhost:36209/>

is not in the

redirect_uris

field, you'll need to add it. You can do this using the

ory update oauth2-client {client.id}

command and providing the updated

redirect_uris

field. [Source](https://www.ory.sh/docs/hydra/debug#refresh-token-flow-fails) If you're still encountering issues after these steps, it might be helpful to refer to the [Ory documentation](https://www.ory.sh/docs/) for more detailed troubleshooting information.

The

client.id

is a unique identifier for your OAuth 2.0 client. It's typically provided when you first create the client. If you're using the Ory CLI, you can create a new OAuth 2.0 client using the

ory create oauth2-client

command. The output of this command will include the

client.id

(also known as

client_id

). Here's an example command from the knowledge sources:

bash ory create oauth2-client --project "$PROJECT_ID" \   --name "Ory Docs OAuth2 Integration Example Client" \   --grant-type authorization_code,refresh_token,client_credentials \   --response-type code \   --scope openid --scope offline_access --scope email \   --redirect-uri <http://localhost:3000/callback>

After running this command, you should see output that includes the

client_id

. You can then set this as an environment variable for easy access:

bash export OAUTH_CLIENT_ID="{set to the client ID from output}"

If you've already created an OAuth 2.0 client but don't remember the

client.id

, you might need to check the service where you registered the client. Unfortunately, the provided knowledge sources don't include specific instructions for retrieving a forgotten

client.id

. [Source](https://www.ory.sh/docs/getting-started/oauth2-openid/add-oauth2-openid-connect-nodejs-expressjs#prerequisites)