Changes to SuiteTalk Roles and Permissions Are Not Immediately Applied

Description: When permissions for a SuiteTalk-designated role are modified within the user interface, the changes are not immediately applied to web service requests.  This may cause unexpected behavior or errors for production-level integration systems or for general SOAP testing.

As an example, consider a custom role called WS Custom Role that is dedicated for SuiteTalk use.  For illustration, this web services role is given View permissions only to the Customer record type under the role's Permissions > Lists subtab.  If this permission level is changed to Full instead, the effect is not immediately applied to web services, and it may take some time before the new permissions take effect.  In the meantime, an INSUFFICIENT_PERMISSIONS error may be encountered.

When modifying SuiteTalk roles and permissions, a good way to make sure the changes are immediately applied is to switch roles during SuiteTalk execution.  The following steps can be followed:

1.       Change the permissions of a SuiteTalk role as desired.

2.       On the next SOAP request after the role changes are made, do not use the original role in the header Passport.  Instead, use another valid role for the employee.

3.       After using another role, switch back to using the original SuiteTalk role for subsequent requests.

The steps described above forces the web service to clear the cache and use the new role's permissions.  When requests are sent again using the original role, the new permission set takes effect immediately.