We have an ASP Core 2.0 App working nicely with Azure AD on the private network. However, we've been playing around with the Azure Application Gateway, investigating the possibility of allowing access to the app from outside for remote workers etc.
We have registered the app on the Gateway, and, once logged in with Azure AD, the anonymous front page is accessible via ourapp.msappproxy.net
. However, when signing in (again?) in the app, the client is redirected back to intervalServer/signin-oidc
which fails as it is not accessible externally.
While I doubt this is any part of the solution, I have tried overriding the redirect "CallbackPath": "/signin-oidc",
to absolute path ourapp.msappproxy.net/signin-oidc
but I can't seem to work out how. Changing the reply URL in Azure Portal doesn't help either (although I doubted it would, this is just for verification right?).
I can't seem to find any guidance on this on this particular scenario, so that would be welcome. Otherwise, I'm left pondering the following:
1, If I could change the redirect to ourapp.msappproxy.net/signin-oidc, would that solve the sign in issue?
2, Do I even need an additional sign in step, or should I be changing the app to accept AzureAppProxyUserSessionCookie
or AzureAppProxyAccessCookie
? (If that's even an option?)
&redirect_uri=https://localhost/44305/test'
viaAppSettings
->"CallbackPath": "/test"
. However, I cannot specify an abolute path (which wouldn't be ideal anyway, but just for testing), as I get exceptionthe path in 'value' must start with '/'.