EIB/Integration Launch Fails: "Response 500 - The Task Submitted Is Not Authorized"
The error Response :500 : Processing error occurred. The task submitted is not authorized.
What it means
The Integration System User (ISU) running the integration doesn't have permission to execute the underlying task or custom report the integration depends on - it's not a config or mapping problem, it's a security domain gap that only shows up when the ISU (not an admin) runs it.
Troubleshooting
- Confirm the integration runs fine under an admin account but fails under the ISU - this confirms a permissions gap, not a data/mapping bug.
- Check whether the ISU's security group is added to the correct permission section: Integration Permissions alone is not enough if the integration calls a custom report or business process task directly - it also needs Report/Task Permissions on that specific domain.
- Identify exactly which object the integration calls last (a custom report, a BP task, a web service operation) and check its specific security domain for the ISU's group.
- Re-test after adding the group to Report/Task Permissions rather than only Integration Permissions.
⚡ Quick fix
Add the ISU's integration security group to the Report/Task Permissions section (not just Integration Permissions) of the domain guarding the object being called.
✓ Permanent fix
When building an ISU security group for a new integration, map out every object it touches (reports, BPs, web services) and grant it in every relevant permission section up front, instead of only the Integrations section.
Was this helpful?