Issue with proxy and oidc (Discord)

[thecodeassassin]

Hi,

We are currently using Kratos (via Ory Cloud) to build our user system. We want to offer our users the following sign-in/registration methods:

• Email
• Discord
• Twitch
• Google Account

We successfully added Discord via the guide on this page:

https://www.ory.sh/docs/guides/social-signin/discord#mapping

But it's never redirecting back to my local environment. It always redirects to

https://<ory-cloud-project-slug>.projects.oryapis.com/self-service/methods/oidc/callback/discord

How can i configure Kratos to always redirect back to the domain I am testing on (in this case my local domain). The local URL is added in the allowed redirects in Discord. We'd like the login to return us to the same URL we set in the ?return_to query parameter when we start the signin flow.

We are running Ory Proxy locally, everything works fine for email authentication.

[aeneasr]

Unfortunately you have found one of the limitations we are currently facing with OIDC on local systems :( It is at the moment not possible to perform OIDC flows when using the Ory Proxy / Ory Tunnel. We are still trying to figure out how to address this.

One way to do it manually is to just change the URL in the browser:

-https://<ory-cloud-project-slug>.projects.oryapis.com/self-service/methods/oidc/callback/discord?code=...
+http://localhost:5000/self-service/methods/oidc/callback/discord?code=...

[thecodeassassin]

Hi,

Thanks for coming back to me.

When do I change the URL?

After login I get this URL:

https:///projects.oryapis.com/ui/error?id=29980b51-da80-4059-9acd-66f6e2c5d799

If I do it with the code returned I get this:

{
  "code": 400,
  "message": "The request was malformed or contained invalid parameters",
  "reason": "Unable to complete OpenID Connect flow because the OpenID Provider did not return the state query parameter.",
  "status": "Bad Request"
}

Also, this means we cannot go to production with this solution. How can we fix this in the short term? We need to release next week so I don't have a lot of time. If we cannot figure this out we have to go with Auth0. Once we go live with a provider it won't be trivial for us to switch and we'd rather use Ory.

[aeneasr]

Hi, for production please set up a custom domain which will set up everything correctly for social sign in to work!

For your question on localhost, if you inspect the network traffic on google chrome dev tools you will find an URL like the one mentioned in my comment. If you copy that and replace the host to your local host, it should work. It's a bit of a messy workaround but unfortunately the best I have got for your tight timeline right now :)

We're tracking a fix for getting social sign in to work with Ory CLI here: #113