IdentityServer / IdentityServer4

OpenID Connect and OAuth 2.0 Framework for ASP.NET Core
https://identityserver.io
Apache License 2.0
9.23k stars 4.02k forks source link

What should be the callback URL for AAD as an external identity provider for identity server 3? #5388

Closed mridulla closed 2 years ago

mridulla commented 2 years ago

Question

I'm trying to build a standalone identity server that is catering to multiple customers and am using the "auth code" response type with AAD as an external identity provider. So, my client calls the identity server, which then calls to the AAD for authentication. This is happening successfully as the AAD is returning the code back. I am expecting that the callback should return back to Identity Server 3 which would then redirect back to my client.

As of now, I am facing an error here. What should be the callback URL for AAD as an external identity provider for identity server 3?

I have tried multiple callback URLs like "/signin-oidc" and also "/signin-aad". Also, have the same redirect URI in the registration App. However, it gives me the HTTP 404 error "The resource cannot be found.".

Can someone please help me what should be the value in callback so that the identity server recognizes and further processes the response for the "authorize" endpoint from the AAD?

The method "AuthenticateExternalAsync" is also not hit once the authentication is successful.

Minimal working example

Please find attached files that have startup files along with user service.

IdentityServerInfo.zip

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Questions are community supported only and the authors/maintainers may or may not have time to reply. If you or your company would like commercial support, please see here for more information.

github-actions[bot] commented 2 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.