Further Secure the Inbound HTTP Request External Integration URLs
External integration users require the correct permissions to use non-UI external integration http request URLs. If proper access entry points are not given to the user then failures will occur.
By default, all of the non-UI external integration http request URLs are grouped into a child access control list of "External Integration". There is a User Role of "INTEGRATION", a parent level access control list of "INTEGRATION" and a child level "External Integration" access control list which all have been created by default so you can easily assign or extend just the external integration related access control entry point to your external integration users depending on the access needs to other parts of the service.
Depending on your current user role and access control list assignment strategy and business needs, you need to determine if you should use the "INTEGRATION" user role, the parent level "INTEGRATION" access control list or the child level "External Integration" access control list. It is best to isolate the true external integration only users from other parts of the service by using one of these. You may even want to consider a custom ACL which only grants the specific integration http request URL(s) required.
List of non-UI HTTP Request External Integration URL entry points:
glog.integration.servlet.DBXMLServletglog.integration.servlet.ExternalSystemServletglog.integration.servlet.TransformerServletglog.integration.servlet.WMServletglog.integration.servlet.BatchCSVUtilServletglog.integration.servlet.DirLoadServletgtm.integration.itm.servlet.ITMIntegrationServlet