mikehardie | 2022-06-09 23:56:17 UTC | #1
Hi Folks, not sure this is the correct place to log a bug but here goes.
Using the POST /api/v2/authorization/roles API, some content causes it to back screen.
We have successfully used this API to create other roles but one role in particular caused the window to open to full screen black and no content. Using Chrome Version 102.0.5005.63 (Official Build) (64-bit). The same content works correctly using the legacy API explorer
The content is below.
Great tool otherwise.
Mike
{ "name": "XXX Limited Admin", "description": "DO NOT DELETE (XXX Managed) \nXXX Limited Admin role for OAuth with rights to create, delete and modify OAuth’s", "permissionPolicies": [ { "domain": "integration", "entityName": "customEmbeddableFramework", "actionSet": [ "" ], "allowConditions": false }, { "domain": "integration", "entityName": "botconnector", "actionSet": [ "" ], "allowConditions": false }, { "domain": "integration", "entityName": "emailPreviewApps", "actionSet": [ "" ], "allowConditions": false }, { "domain": "integration", "entityName": "unifiedCommunications", "actionSet": [ "" ], "allowConditions": false }, { "domain": "integrations", "entityName": "", "actionSet": [ "" ], "allowConditions": false }, { "domain": "integration", "entityName": "serviceJourneyApps", "actionSet": [ "" ], "allowConditions": false }, { "domain": "oauth", "entityName": "", "actionSet": [ "" ], "allowConditions": false }, { "domain": "authorization", "entityName": "", "actionSet": [ "" ], "allowConditions": false }, { "domain": "integration", "entityName": "presence", "actionSet": [ "" ], "allowConditions": false } ] }
jacobshaw | 2022-06-10 15:10:23 UTC | #2
Hi @mikehardie Customer Care is the place to go to report bugs, but I work directly with the API Explorer so I can field this. Right now it's looking like some of the characters in the request body are breaking it, since I get this in part of the error logs: "The string to be encoded contains characters outside of the Latin1 range." At a glance, some of the lines are italicized which may be the reason. It's not ideal to show a blank screen when the characters are unparsable, so I will make sure this is the cause and then report it to my higher-ups and see what can be done.
mikehardie | 2022-06-14 00:03:28 UTC | #3
Hi Jacob, the data being posted is from an export of a role in another org. Some of the chars seem to create markdown
jacobshaw | 2022-06-14 00:54:18 UTC | #4
@mikehardie The fix will handle different special character types, so the text should convert without errors once the fix is deployed
system | 2022-07-15 00:55:02 UTC | #5
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: 15084