Workflow Credentials Issue with Transformation

​@Leandro de Lima Almeida I’ll check on this with the engineering team and get back to you with an update.

Hi ​@Leandro de Lima Almeida, thanks for reaching out. 

Just to make sure I understand the challenge correctly:

You would like to use a set of credentials to trigger/start your workflow, but one or more Transformation tasks within the workflow should use a different set of credentials (which in this case would be the same set of credentials that are configured on the Transformation)?

Meaning if a Transformation has a set of client credentials configured, you’d like the workflow to execute the Transformation using this set?

Hi, ​@Jørgen Lund 

Exactly.
Similar to when a transformation is executed using the Python SDK inside a Cognite Function, the client credentials configured in the transformation are used to execute it.

The client credentials used by the transformations in our project have a broader set of capabilities assigned to them.

Thanks ​@Leandro de Lima Almeida, we’ll look into this and get back to you.

​@Jørgen Lund, ​@Leandro de Lima Almeida I’ll convert this to a product idea.

do we have an update?

Hi ​ ​@Leandro de Lima Almeida ​@ibrahim.alsyed - we’re making this a priority and starting implementation next week. 

Hey ​@Leandro de Lima Almeida ​@ibrahim.alsyed .

This is now available through the workflows API and Cognite Python SDK (7.73.0). On a transformations task parameters, you can now set `useTransformationCredentials` (boolean, default false). 

• -If set to `true`, the transformation will run using the client credentials configured on the transformation.
• If set to `false`, the transformation will run using the client credentials used to trigger the workflow. Which was the previous behavior.

This feature will be available in the UI soon, the team is working on it now.

Thank you all for the support and the quick response.

I’ll make the change in the current workflows.