In the Collaborate 4.2 release notes we omitted an important piece of information about a change in configuration which we have made to bring API security inline with the Collaborate UI.

There are four site security options:

• Password protected site
• 2FA enabled site
• Terms & Conditions
• IP restricted site

When enabled, each security option restricts the Collaborate user from accessing the site unless they comply with those security restrictions e.g. enter the password or accept the terms and conditions. We do not currently have API endpoints to process those settings using the API, so before Collaborate 4.2 we ignored those settings for API calls.

In order to make sure that our API follows the same security settings as the core application, we have enabled those site restrictions through the API i.e if the site has any of those 4 site restrictions in place then the API client will not be able to access content from that site.

Please note that we have the capability to switch this restriction off from the API, however, this has to be an explicit action from the integrator or client, so please let us know if this is an issue for your integration and raise a support ticket at support@highq.com to disable this API configuration.

We plan to provide API endpoints which will emulate the UI workflow of accepting these site restrictions.