We currently only use the Web GUI on which we apply a maximum of 1 concurrent users per account, to prevent account sharing. This works great, except that we actually planning on developing an application on top of the rest API of Indicium.
What can happen is the following:
The user is logged in in the Web GUI. We have developed a plug-in for another piece of software to generate an export file. This export file can be exported in the plug-in and uploaded again in the Web GUI. But instead of all those manual actions of exporting, uploading (several clicks), we want to allow the user to directly upload that export file.
This is already possible using the Indicium OData API, so that's achieved. Problem is that when you are logged in in the Web GUI client, you will get a http 403 error in the Indicium plug-in on each call when you’re also logged in in the Web GUI, due to the concurrent access restriction. Off course this is by design I guess, but prevents us from add some really valuable extras to our software.
What we actually want is an exception for that specific application using Indicium. This application has a limited set of function calls (a few get calls for listing data and a post call to a task). Is this possible, or somehow to work around?
Best answer by Anne Buit
This is indeed currently not possible by design. The concurrent access system does not distinguish between different clients. Making an exception for Indicium will cause trouble in the future when the Universal GUI is used, as Indicium is used as back-end for Universal.
However, you can work around it in a different way.
You can create a second application in IAM without the concurrent access restrictions. This application uses the same project version and database but a different alias and only grant the users access to the role granting for the upload API. The plug-in will have to be updated to refer to the nonrestricted application.
In doing so, only the uploading will be unrestricted.