In the current implementation we can successfully execute any QL command that arrives at the polystore regardless whether authorisation tasks are present. The integration api should just create the PreEvent object and execute only those PreEvents that have arrived at the AUTH queue (via custom authorisation tasks that will be written by users of the polystore or a possible default authorisation task accepting all of them) and their isAuthenticated flag is true.
In the current implementation we can successfully execute any QL command that arrives at the polystore regardless whether authorisation tasks are present. The integration api should just create the PreEvent object and execute only those PreEvents that have arrived at the AUTH queue (via custom authorisation tasks that will be written by users of the polystore or a possible default authorisation task accepting all of them) and their isAuthenticated flag is true.