Hi @Hennessy, Tim I have got the following feedback from the product team on this issue. The error message that you notice seem to indicate that you are trying to use that secret directly without storing the value in KV. This is a scenario where we expect to see that error. Product team has confirmed that this is NOT a flow that is allowed in Data Processor today. We do not support providing plain text secrets directly.
The secrets that are used by the pipeline have to be stored in the KV and the aio-default-spc should be updated with the secret name. This secret name should then be provided as the client secret.
I appreciate if you can try the above suggested approach and let us know if you still experience this issue.
If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.