Leah_Goddard | 2018-10-30 10:27:58 UTC | #1
We have been developing a web-based tool.
One of the features (“Unassign a user assigned to a station”) used by the new tool is not working as expected. In the same way that current tool is using Client Credentials OAuth to manage permissions based on configured roles, if we use the new tool with the same roles associated, the unassign option is not working as expected offering an “status: 403, statusText: "Forbidden"”
As per following article, referred feature requires different permissions than the current solution. https://help.mypurecloud.com/articles/deprecation-access-control-based-role-name/
We cannot assign “telephony:plugin:all” permissions to our Supervisors because then they would be able to edit Telephony options.
Is there a solution to this? maybe a permission that can unassign, but doesn't get the rest of the permissions given in telephony all?
tim.smith | 2018-10-30 13:16:08 UTC | #2
The 403 error is because you're lacking some permission. The error body will generally tell you what permission the API requires. If you are unwilling to assign the permissions required for the API to your users/roles, you can suggest more granular permissions and share your use case at https://purecloud.ideas.aha.io/ideas.
system | 2018-11-30 13:16:10 UTC | #3
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: 3850