Issue: "Velusia" sample code does not work

Question

Issue: "Velusia" sample code does not work

robertkhou opened this issue 4 years ago · comments

Robert Chanphakeo commented 4 years ago

Sample code for "Velusia" client/server project is not working as expected.

To reproduce

Download sample code
Run both Velusia Server and Velusia Client
Client on "Sign in" button via Velusia client web app

Error

invalid_request The specified 'redirect_uri' is not valid for this client application.

"warn: OpenIddict.Core.OpenIddictApplicationManager[0]
Client validation failed because 'https://localhost:44338/signin-oidc' was not a valid redirect_uri for mvc.
fail: OpenIddict.Server.OpenIddictServerDispatcher[0]
The authorization request was rejected because the redirect_uri was invalid: 'https://localhost:44338/signin-oidc'."

note: After verifying the server project, it was found that https://localhost:44338/signin-oidc is actually a valid redirect uri

Kévin Chalet · Answer 1 · Thu Dec 24 2020 21:31:34 GMT+0800 (China Standard Time)

I suspect you're simply using an obsolete clone or are not taking a look at the right branch (dev).

Robert Chanphakeo · Answer 2 · Thu Dec 24 2020 22:15:13 GMT+0800 (China Standard Time)

The sample code if from "dev" branch, and I just verified the project uses .NET 5 and its running OpenIddict 3.0.0

I redownloaded the sample code from the "dev" branch, i'm getting the same error message as described above.

Kévin Chalet · Answer 3 · Thu Dec 24 2020 22:18:44 GMT+0800 (China Standard Time)

Is there a chance you're running the sample with a database created a while ago, when the redirect_uris were not HTTPS address? Try to delete and recreate the DB.

Robert Chanphakeo · Answer 4 · Thu Dec 24 2020 22:43:41 GMT+0800 (China Standard Time)

I just checked the database records and it was using http rather than https, (this might have been from a previous version), a quick database update resolved the issue! 👍

Kévin Chalet · Answer 5 · Thu Dec 24 2020 22:54:58 GMT+0800 (China Standard Time)

Great to hear!

…

Le 24 déc. 2020 à 15:43, Robert Chanphakeo ***@***.***> a écrit : I just checked the database records and it was using http rather than https, (this might have been from a previous version), a quick database update resolved the issue! 👍 — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

Thomas Dam · Answer 6 · Thu Jan 06 2022 23:50:48 GMT+0800 (China Standard Time)

Hi, I am currently having this same problem trying to replicate this project in NET 5.0. The only difference is my project is not using Quartz.

As you guys discussed before, I have checked the redirect_uri value in my database and my OpenIddictApplications.RedirectUris value is:
["https://localhost:44338/signin-oidc"]

When I run click "Sign in", after returning a challenge from /login, it doesn't even hit the /connect/authorize endpoint and gives me the same error:
The specified 'redirect_uri' is not valid for this client application.

Any ideas? Maybe the exclusion of Quartz has broken something in my project? Thank you.

Thomas Dam · Answer 7 · Fri Jan 07 2022 17:23:44 GMT+0800 (China Standard Time)

Hi, I am currently having this same problem trying to replicate this project in NET 5.0. The only difference is my project is not using Quartz.

As you guys discussed before, I have checked the redirect_uri value in my database and my OpenIddictApplications.RedirectUris value is: ["https://localhost:44338/signin-oidc"]

When I run click "Sign in", after returning a challenge from /login, it doesn't even hit the /connect/authorize endpoint and gives me the same error: The specified 'redirect_uri' is not valid for this client application.

Any ideas? Maybe the exclusion of Quartz has broken something in my project? Thank you.

I fixed my problem. It turns out I was using the server url instead of the client url for the RedirectUris database values. Now it is able to hit the /connect/authorize endpoint.