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

Deployment > Servers > [Server] fails to load


    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 14.0.0
    • Fix Version/s: 14.0.0
    • Component/s: sms, XUI


      Attempting to access the server configuration page for a single server results in an error "Bad request error."

      Steps to reproduce:

      • Install OpenAM using default configuration
      • Navigate to Deployment > Servers > [named server]
      • Error occurs, response from server is:
        {"code":400,"reason":"Bad Request","message":"Server name not specified."}

      Excepted Result:

      • Server configuration page loads

      Note: If there are multiple servers in a cluster this error does not occur. It appears to be specific to having only a single server configured. Perhaps an avenue of investigation might be to compare how the clustered deployment differs from a single deployment.


      The request that fails is as follows:

      Request Headers

      POST /openam/json/global-config/servers/01/properties/general?_action=schema HTTP/1.1
      Host: rwapshott.forgerock.com:8080
      Connection: keep-alive
      Content-Length: 0
      Pragma: no-cache
      Cache-Control: no-cache
      Accept-API-Version: protocol=1.0,resource=1.0
      Origin: http://rwapshott.forgerock.com:8080
      User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
      Content-Type: application/json
      Accept: application/json, text/javascript, */*; q=0.01
      X-Requested-With: XMLHttpRequest
      DNT: 1
      Referer: http://rwapshott.forgerock.com:8080/openam/XUI/
      Accept-Encoding: gzip, deflate
      Accept-Language: en-US,en;q=0.8
      Cookie: JSESSIONID=2659D2A04335F7D1E1DAF079C0D66C91; AMAuthCookie=AQIC5wM2LY4Sfcy4L7SR-Fd9SS8eb7_yhQicJT-EMum1gbk.*AAJTSQACMDIAAlNLABQtODAyNzU0MjI1NjMxMDM2MTc0OAACUzEAAjAx*; i18next=en-US; amlbcookie=01; iPlanetDirectoryPro=AQIC5wM2LY4SfczTfWZNPVBvbKBKaUqxuEHRY3TNsBdFH9Y.*AAJTSQACMDEAAlNLABM4NzQxNzA4MDExMjY2MTkwMDIzAAJTMQAA*

      Response Headers

      HTTP/1.1 400 Bad Request
      Server: Apache-Coyote/1.1
      Cache-Control: no-cache
      Content-API-Version: resource=1.0
      Content-Type: application/json;charset=UTF-8
      Transfer-Encoding: chunked
      Date: Wed, 27 Jul 2016 16:15:19 GMT
      Connection: close

      Example CuRL Script to reproduce the issue:

      LOGIN_RESULT=`curl --request POST --header "X-OpenAM-Username: amadmin" --header "X-OpenAM-Password: $ADMIN_PASS" --header "Content-Type: application/json" --data "{}" $SERVER/json/authenticate 2>/dev/null`
      TOKEN_SPLIT=`echo $LOGIN_RESULT | sed -e 's/[{}:,\"]/ /g'`
      TOKEN=`echo "$TOKEN_SPLIT" | cut -d " " -f 6`
      curl --request POST --header "iplanetDirectoryPro: $TOKEN" $SERVER/json/global-config/servers/01/properties/general?_action=schema




            • Assignee:
              rwapshott Robert Wapshott
              rwapshott Robert Wapshott
              QA Assignee:
              Filip Kubáň [X] (Inactive)
            • Votes:
              0 Vote for this issue
              2 Start watching this issue


              • Created: