TheRealKevinGlinski | 2022-01-03 15:04:13 UTC | #1
When deleting/inactivating a user, you have the ability to set a reason for the state change (Voluntary, seasonal, leave, performance, etc). This change calls PUT /api/v2/users/{userId}/state and requires the directory:user:edit permission.
There is a resource GET /api/v2/users/{userId}/state to get that state information, but requires the directory:userStateChange:view permission. I don't see that permission in my org, can someone confirm if the enforced permission is correct or if I need to contact care to find out why that permission doesn't exist in my org?
Thanks, Kevin
Eos_Rios | 2022-01-03 15:32:04 UTC | #2
Permission is real/enforced.
{ "message": "Unable to perform the requested action. You must have at least one of the following permissions assigned: [directory:userStateChange:view] in at least one of the following division(s): [redacted]", "code": "forbidden", "status": 403, "contextId": "redacted", "details": [], "errors": [] }
And I don't see it in the list either.
tim.smith | 2022-01-03 21:32:12 UTC | #3
@TheRealKevinGlinski The permission on that resource isn't correct. There's some cleanup that needs to be done that was missed during the transition to released for that endpoint. It shouldn't take long to fix, but has to work it's way to production. If you need a more precise timeline or want to monitor the status, you can open a case with Care and reference COPY-1060.
system | 2022-02-03 21:18:20 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 13106