- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2024 09:45 PM
Hi, unfortunately without clear details of your configuration or payloads from both scenarios there is little to evaluate.
Is your API using a single integration account for authentication? or are you authenticating with details from individual users? If using 1 auth account have you confirmed that the individual users have access to the underpinning data\records and that the payload they generate is complete and aligned with a payload generated by an admin user?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2024 10:26 PM
Hi Tony, Yes my API is a single integration account with Auth 2.0 authentication type.
Our User has all the rights to access the data of incident table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2024 11:23 PM
Hi,
This is the payload that we have been sending over.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2024 03:48 AM
Hi,
I got this issue fixed, just in case anyone want to refer in future.
401 is a permission issue, ITIL User's were not able to see record entry on the oauth_credential table, so when they try to ebond tickets they never ebonded to the 3rd party.
To fix this create acl both on the table and field level with role itil, now test the ebond it should work!
Thank You!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2026 12:31 PM
Hi,
Could you please share few details like what kind of ACL should be created and I guess we need to create ACL on the instance from which we are trying to send the data ?