
- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-07-2021 10:23 AM
Failed API level ACL Validation - 403 Forbidden error
When we're trying o connect on the web servisse. Are you getting this error?
Steps to reproduce: Connect using some programming tool OR API Explorer
- >> System Web Services > REST > REST API Explorer
2. Select
3. Select your table
4. Send
IF you get this answer: - response body
{
"error": {
"detail": "Failed API level ACL Validation",
"message": "User Not Authorized"
},
"status": "failure"
}
Check this configuration: - solution
01. Navigate to >> System Definition Tables
02. Select your table
03. Open Application Access TAB
04. Change Accessible from to "All application scopes"
KB0686244 - When you impersonate a user and then try to re-impersonate your own user account, the Impersonate User popup window shows an error Failed API level ACL Validation
KB0752345 - Service Portal: Order confirmation screen does not allow ITIL users to change the "Request for" field.
KB0745354 - Unable to access list view of records in mobile app
KB0726447 - Impersonation not working for certain users
KB0713041 - Cannot impersonate a user (redirected to login page)
- 5,530 Views
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hey Tiago,
I am trying to query sys_plugins table, but getting the very same error:
> curl -H 'Authorization: Bearer <TOKEN>' 'https://<INSTANCE>.service-now.com/api/now/v1/table/sys_plugins'
{"error":{"message":"User Not Authorized","detail":"Failed API level ACL Validation"},"status":"failure"}
This is the table config
This is the access rule I have created
Any idea what is missing?
Thanks!
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi Tiago and other experts,
We get this issue with 403 error and the same
{
"error": {
"detail": "Failed API level ACL Validation",
"message": "User Not Authorized"
},
"status": "failure"
}
But we checked all the configurations on the table at Application Access Tab, everything is right. We still get these 403 errors. Do you or other experts have any other suggestions to solve these issue?
Thanks lot!
Jerry