AIO data pipeline clientSecret pattern match

Hennessy, Tim 25 Reputation points
2024-03-29T19:02:10.3333333+00:00

I am working through an Azure IoT Operations QuickStart article regarding the Data processor. Towards the end of the exercise, a transform shape is used to push the data to Fabric. The credentials include the clientSecret that is generated via az ad sp create-for-rbac --name {spn}

that password contains, in my case, a tild (~) symbol which is not allowed in the pattern match by AIO. I did some digging into recreating a client secret but I find no way to control what symbols get generated. Furthermore, if the password is allowed in Azure AD, why is necessary to have a different pattern match in AIO?

So, I'm stuck again. Are there any steps I can take to generate a clientSecret that would be compatible with AIO? Or is there any steps I can take to force AIO to allow the clientSecret I have?

AIO data pipeline clientSecret pattern

appreciate the help.

Azure IoT Operations
Azure IoT Operations
Azure IoT Operations is a set of modular services enabled by Azure Arc.
14 questions
Accepted answer
  1. LeelaRajeshSayana-MSFT 13,951 Reputation points
    2024-04-01T19:20:13.7966667+00:00

    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.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest