Last post Nov 18, 2019 12:56 PM by HarryPfleger
Nov 17, 2019 09:13 AM|HarryPfleger|LINK
I cannot authenticate from an external client (browser) to an internal
ASP.NET 3.0 web site, where authentication is using IdentityServer 4.
The web site is behind a Microsoft WAP (Web Application Proxy).
I get a: 503 - Service Unavailable
Is this by design?
Are there option to authenticate in such an environment?
Nov 17, 2019 02:08 PM|mgebhard|LINK
A 503 error means the service is under maintenance or too busy to respond. Can you explain how your application works? What does internal and external mean in your application? Intranet/Internet?
Nov 18, 2019 08:27 AM|HarryPfleger|LINK
Thankx mgebhard for your feedback.
internal = intranet | external = internet
I can authenticate, when I am internal, but I can't when I am external. The traffic has do go through WAP (web application proxy).
The following URL gets a 503 response when external, from internal it returns the result (200)
Nov 18, 2019 11:49 AM|mgebhard|LINK
I'm not sure how this is an ASP.NET question. I believe you need networking or Windows Server support.
Nov 18, 2019 12:56 PM|HarryPfleger|LINK
You have probably right. That is mostly the problem when the issue is not related to just one product.
But at least, there could be users around, which have a similar setup and maybe have it working, or tried and did not find a solution.
Or the ASP.NET team knows about this issue and knows how to solve it, or not ;-)
PS: If I cannot find a solution in the community, I will open a case with Microsoft.