Running ASP.NET 3.0 Identity behind WAP (Web Application Proxy) RRS feed

  • Question

  • User1326661867 posted

    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?

    Thankx, Harry

    Sunday, November 17, 2019 9:13 AM

All replies

  • User475983607 posted

    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?

    Sunday, November 17, 2019 2:08 PM
  • User1326661867 posted

    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)


    Thankx, Harry

    Monday, November 18, 2019 8:27 AM
  • User475983607 posted

    I'm not sure how this is an ASP.NET question.  I believe you need networking or Windows Server support.


    Monday, November 18, 2019 11:49 AM
  • User1326661867 posted

    Thankx mgebhard.

    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 ;-)

    Thankx, again.

    PS: If I cannot find a solution in the community, I will open a case with Microsoft.

    Monday, November 18, 2019 12:56 PM