Layer7 API Management

Expand all | Collapse all

Error Accessing the Oauth Manager

  • 1.  Error Accessing the Oauth Manager

    Posted 02-19-2019 05:20 AM

    Hi,

    I am getting below html page,while accessing the oauth manager page:

    Below are the logs :

     

    • 2019-02-19T15:47:53.986+0530 INFO 520 com.l7tech.server.MessageProcessor: Request URL not resolved: https://***:8443/favicon.ico
    • 2019-02-19T15:47:59.525+0530 SEVERE 527 com.l7tech.server.SoapMessageProcessingServlet: Assertion not available: Code not available for assertion: CustomAssertion
    • 2019-02-19T15:47:59.528+0530 WARNING 527 com.l7tech.server.util.SoapFaultManager: Ignoring invalid http status code for fault ''.
    • 2019-02-19T15:47:59.541+0530 WARNING 527 com.l7tech.server.util.SoapFaultManager: Ignoring invalid content type for fault '', MIME Content-Type header missing or empty.
    • 2019-02-19T15:48:01.132+0530 INFO 531 com.l7tech.server.MessageProcessor: Request URL not resolved: https://***:8443/favicon.ico
      • 2019-02-19T15:48:25.388+0530 INFO 35 com.l7tech.external.assertions.ratelimit.server.ServerRateLimitAssertion: Removing stale rate limiter https://***:8443/g2/oauth/manager

    Thanks.



  • 2.  Re: Error Accessing the Oauth Manager

    Posted 02-19-2019 05:26 PM

    I remember it's a known bug.

    You actually have error on OTK, the OTK returns an error page, its content-type should be html, but uses wrong content-type as plain text, therefore the browser shows the html source code.

    You can try to save to html code as a xx.html file, and open with browser, then you should see the error the OTK returned.



  • 3.  Re: Error Accessing the Oauth Manager

    Posted 03-02-2019 01:47 AM

    Hi Zhijun,

    I tried to install OTK4.0,4.1,4.2, still getting the same issue.

    Please help

     

     

    Thanks.



  • 4.  Re: Error Accessing the Oauth Manager

    Posted 03-03-2019 06:22 PM

    Okay, this is the correct error page it should show (not html source code), but the error page doesn't tell much about the error.

    First of all, you may double check if the post-install tasks have been done,

    Post-Installation Tasks - CA API Management OAuth Toolkit - 4.2 - CA Technologies Documentation