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

REST Endpoint /json/subjectattributes not working as documented

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 6.0.0.2, 6.5.0
    • Fix Version/s: None
    • Component/s: API descriptor
    • Labels:
    • Rank:
      1|hzw9i7:
    • Support Ticket IDs:

      Description

      Bug description

      In the AM-6-Authorization Guide on page 91 is a example on how to use the REST interface to query the subjects attributes. The example shows an "Accept-API-Version" header which does not work. When the example is executed the response is a 

      _{
      "code": 500,
      "reason": "Internal Server Error",
      "message": "Can not start an object, expecting field name (context: Object)"
      }_

       

      How to reproduce the issue

      Details steps outlining how to recreate the issue (remove this text)

      1. Execute the example as described on page 91. and substitute the cookie value with a valid one. 
      2. OR, use the API-Explorer. This gives the same error message.

       

      $ curl \
      
      --header "iPlanetDirectoryPro: AQIC5..."
      
      \
      
      --header "Accept-API-Version: resource=1.0" \
      
      https://openam.example.com:8443/openam/json/realms/root/subjectattributes/?_queryFilter=true
      
      {
      
      "result" : [
      
      "sunIdentityServerPPInformalName",
      
      "sunIdentityServerPPFacadeGreetSound",
      
      "uid",
      
      "manager",
      
      "sunIdentityServerPPCommonNameMN",
      
      "sunIdentityServerPPLegalIdentityGender",
      
      "preferredLocale",
      
      "...",
      
      "...",
      
      "..."
      
      ],
      
      "resultCount": 87,
      
      "pagedResultsCookie": null,
      
      "remainingPagedResults": 0
      
      }
      

       

      Expected behaviour
      List of attributes
      
      Current behaviour
      {
      "code": 500,
      "reason": "Internal Server Error",
      "message": "Can not start an object, expecting field name (context: Object)"
      }
      

      Work around

      If you provide the correct Header ""Accept-API-Version: protocol=1.0,resource=1.0" " it works. 

       

      Code analysis

      Please also update the documentation and the api-explorer.

       

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            vkoldenh Vincent Koldenhof
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Dates

              Created:
              Updated: