Incapsula incident ID error when using OData with OAuth authentication
I have configured an OAuth account in Creatio. When I submit OData requests using Postman from my local environment, the request fails with the following error:
“Request unsuccessful. Incapsula incident ID:
Has anyone encountered this issue before?
I would like to understand whether this error is typically related to a misconfiguration on the Creatio side (for example, OAuth, user permissions, IP restrictions, or OData settings), or if it requires additional configuration or whitelisting on Creatio’s infrastructure side related to Incapsula.
For context:
- The request is executed successfully from Postman locally, but consistently fails with the Incapsula error.
- Authentication is performed via OAuth.
- No detailed error response is returned beyond the Incapsula incident ID.
Any guidance or similar experiences would be greatly appreciated.
Like
Hello,
Could you please provide an extended version of the error to better understand the issue?
Sure. When making the call in Postman to https://my-instance.creatio.com/0/odata/MyTable
I get a 200 code but with the following message:
<html style="height:100%">
<head>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<meta name="format-detection" content="telephone=no">
<meta name="viewport" content="initial-scale=1.0">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
</head>
<body style="margin:0px;height:100%"><iframe id="main-iframe"
src="/_Incapsula_Resource?SWUDNSAI=31&xinfo=14-9563318-0%200NNN%20RT%281768398783812%2013%29%20q%280%20-1%20-1%20-1%29%20r%280%20-1%29%20B12%2811%2c748823%2c0%29%20U6&incident_id=153000480030609553-52193177030429710&edet=12&cinfo=0b000000&rpinfo=0&cts=6xwb1BMLFPW1EJ%2bmvV8UDNe2KFWyjZg%2fdeMlMfjgnZf9Xsa1RPnzOa2voMOgSfpa&cip=<my ip>&mth=POST"
frameborder=0 width="100%" height="100%" marginheight="0px" marginwidth="0px">Request unsuccessful. Incapsula
incident ID: 153000480030609553-52193177030429710</iframe></body>
</html>
Rommel Bocker,
I see that you also registered this issue directly for the support team and we have already provided a solution there. I will add the solution here as well.
The error you have encountered seems to be incorrect interpretation of the message that Creatio sent in response to the request. We have tested the provided example request with Postman and identified two blockers.
First request returned with the message: "Current user does not have sufficient permissions to use OData."
To fix this "Access to OData" operation permission need to be enabled for this user.
Then next request returned with the message": "Insufficient permissions to add record in object \"UsrObject\"."
To fix this you need to enable operation permissions for the object and configure it in a way to allow this technical user with a permission to create new records. This is valid only for creation of the new records with POST requests. Please refer to this article.
Thank you for your question!
Mira... thanks. The problem still remains. That's why I was posting this here, just to check if other people have similar situations and find the solution.