Prevent sending httpheader in REST API connection with custom connection

[coengiesberts_anva]

Hi,

I am have a multi-tenant environment with a REST Connection using the POST method. This REST Connection connects to the Qlik Cloud tenants and is available on all tenants. It contains the Authorization query headers in the details of the connection.

I would like to use this connection for launching an automation. I do this as follows:

SQL SELECT
"status"
FROM JSON (wrap on) "root"
WITH CONNECTION (
URL "$(vTenantUrlAlias)/api/v1/automations/$(vAutomationId)/actions/execute?X-Execution-Token=$(executionToken)&appitemid=$(vAppItemId)&tagname=$(vTagName)"
);

This API-call uses POST-method and two parameters: the automationid and the execution token. Because of the execution token, no authorization is required. But... by using the connection mentioned above, the Authorization query headers are always sent and for that is returns a 500 server error.

Is there a way to prevent the Authorization query headers being sent, by sort of clearing them for this specific API-request in the WITH Connection statement?

[coengiesberts_anva]

Well, I figured out that I can use URL "$(vTenantUrlAlias)/api/v1/automations/$(vAutomationId)/runs instead. This supports POST and Bearer authentication.

Now this does not allow my OAuth user to run an automation. Http 403 No permission. You don't have sufficient permissions to access this resource.

I checked the OAuth user and all admin:automations and automation scopes are enabled. Is there a way to allow OAuth users to execute automations?