带有 Azure AD 的 IdentityServer 4 作为外部提供者托管在 Kube.netes pod 中

Question

I have created a custom Identity Service that mainly uses Identity Server 4 with Azure AD as an external provider. I have configured azure ad, having all the required ids & secrets and locally was able to authenticate any registered user in Azure.

The problem appears when we deployed that service into Kube.netes.

I have added a public URL like https://myidentitydomain.com/signin-oidc . In a pod, we have a different domain of identity service than public one (be-identity-service), but it is how it works in Kube.netes. Not sure that its the issue connected to reply URL failure. But also my identity service has to be hosted in private.network in Azure.

Really appreciate for any given advice.

Answer 1

When you click on the sign-in button to authenticate with IdentityServer, do look at the URL to see what returnurl was actually sent to it and add it to the client definition.

For example:

https://demo.identityserver.io/Account/Login?ReturnUrl=%2Fdiagnostics