Uploaded image for project: 'OpenAM Agents'
  1. OpenAM Agents
  2. AMAGENTS-1709

JSON Response code and message are incorrect when json inverted mode accesses a not-enforced url.

    XMLWordPrintable

    Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 4.1.0-37
    • 4.2.0.0
    • Web Agents
    • Affects 4.1.x only, doesn't occur in 5.0.1 functional tests.

      Description

      This failure is one of the root causes for the failures of the 4 json validation functional tests.

      I’ve looked into the JSON setting functional tests, and where they all fail is in three ways 1) logic testing for attribute setting involves setting an NEU and then checking the NEU. The expected value is a 404 whereas if the URL inverted logic is being hit, then the a) actual return will be some JSON, and b) the code requested should be set. So if you set inverted_url and the response code to be 202, then you should get back a 202 rather than a 404. This brings me to the second (actual) problem
      2) Actually what is coming back in these cases is a 200 OK which looks like this: {“error”: { “errors”: [

      { “message”: success, “data”: “”"” }

      ], “code”: 0 }}
      this isn’t even valid JSON 3)! This blocks whether the actual test cases work.

      A separate task would be to improve the functional tests so they can handle the returns for the NEUs

        Attachments

          Activity

            People

            mareks Mareks Malnacs
            alex.levin@forgerock.com Alex Levin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: