Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-11190

API Explorer 404 Not Found when behind proxy

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Reopened
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 14.0.0
    • Fix Version/s: None
    • Component/s: API descriptor
    • Labels:
    • Rank:
      1|hztj53:
    • Needs backport:
      No
    • Needs QA verification:
      No
    • Functional tests:
      No
    • Are the reproduction steps defined?:
      Yes and I used the same an in the description

      Description

      Accessing the API Explorer from the AM menu causes a 404 Not Found Error when the deployment is accessed through a reverse proxy.  The API Explorer works if accessing AM directly on the Tomcat port.

      404 Not Found:

      https://idp.frdpcloud.com/openam/json/api/
      

       Request Headers:

      GET /openam/json/api/ HTTP/1.1
      Host: idp.frdpcloud.com
      Connection: keep-alive
      Pragma: no-cache
      Cache-Control: no-cache
      Accept-API-Version: protocol=1.0,resource=1.0
      Accept-Language: en-US
      User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
      Content-Type: application/json
      Accept: application/json, text/javascript, */*; q=0.01
      X-Requested-With: XMLHttpRequest
      Referer: https://idp.frdpcloud.com/openam/XUI/
      Accept-Encoding: gzip, deflate, sdch, br
      Cookie: i18next=en-US; amlbcookie=01; iPlanetDirectoryPro="AQIC5wM2LY4Sfcwl4lwAhLvU2OYPjC0nE9jDso8qVjj99fs.*AAJTSQACMDEAAlNLABMzMzY0NTE4MTI3ODAzMTAyMDUwAAJTMQAA*"
      

      Response Headers:

      HTTP/1.1 404 Not Found
      Date: Wed, 24 May 2017 22:08:36 GMT
      Server: Apache-Coyote/1.1
      Access-Control-Max-Age: 1000
      Access-Control-Allow-Headers: X-Requested-With, Content-Type, Origin, Authorization, Accept, Client-Security-Token, Accept-Encoding
      Access-Control-Allow-Methods: POST, GET, OPTIONS, DELETE, PUT
      Access-Control-Allow-Origin: https://idp.frdpcloud.com
      X-Frame-Options: SAMEORIGIN
      Cache-Control: no-cache
      Content-Type: application/json;charset=UTF-8
      Vary: Accept-Encoding
      Content-Encoding: gzip
      Content-Length: 85
      Keep-Alive: timeout=5, max=98
      Connection: Keep-Alive
      

      Response:

      {"code":404,"reason":"Not Found","message":"Resource 'api' not found"}
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              sfehrman Scott Fehrman [X] (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated: