Manage Access-400 Bad request while adding Entitlement using workflow

Identity Security Cloud (ISC) ISC Discussion and Questions
, , ,
1

Hi Experts,
We have a use case to copy access from a identity and provision same access to new joiner.
While I was able to grab Entitlement from Get Access Action in workflow, I get error while adding that same access using Manage Access. Those entitlements are request able as well. Secondly, I tried using POSTMAN: it throws the same error but from the UI I am able to request the same access and get it without approval or any trouble.
The JSON used from postman using POST req using v3 end point of access-request

{
  "requestedFor": "{id of the identity}",
  "requestType": "GRANT_ACCESS",
  "requestedItems": [
    {
      "id": "{id of the entitlement}",
      "type": "ENTITLEMENT",
      "comment": "tEST"
    }
  ]
}

Response is:

{
    "detailCode": "400.0 Bad request syntax",
    "trackingId": "b9d6b081",
    "messages": [
        {
            "locale": "en-US",
            "localeOrigin": "DEFAULT",
            "text": "The request could not be parsed."
        },
        {
            "locale": "und",
            "localeOrigin": "REQUEST",
            "text": "The request could not be parsed."
        }
    ],
    "causes": []
}

Any lead is appreciated.
Thanks!!

1 Like
4

The error you’re encountering (400.0 Bad request syntax) is due to the incorrect key name in your JSON request body.

5

Hi @SaidurgaMallela

The requestedFor section should be in an array format even though if its for one identity.

example:
“requestedFor”: [“2c9180847e123456017e123456780001”],

@ujjwol_panditAvant confirmed , it is working after above change by himself.

1 Like
6

Hello @ujjwol_panditAvant
Seems that the problem you’re encountering is something pretty common. There are open issues in Github aiming at the same concern. Seems like the Json format is wrongly stated over the documentation as well. I’ve already notified the team and hope they fix this issue soon.

1 Like
7

Hi,
Thank you!
That was me from different account who reported the bug, they will probably fix it soon.

8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.