Open bupt-wenxiaole opened 9 months ago
When you provide the client_id
, we treat it as user assigned managed identity.
Do you want to use system assigned managed identity?
Hi @bupt-wenxiaole. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.
Thanks @xiangyan99 , actually I am not trying to use system assigned managed identity, my point is when I using the user assigned managed identity, the credential passthrough enabled during runtime, this is a bug, suppose the credential passthrough only enabled when prepare_data.identity = UserIdentityConfiguration()
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-ml-sdk @azureml-github @diondrapeck @kdestin @luigiw @MilesHolland @needuv @ninghu @paulshealy1 @singankit @YusakuNo1.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-ml-sdk @azureml-github @diondrapeck @kdestin @luigiw @MilesHolland @needuv @ninghu @paulshealy1 @singankit @YusakuNo1.
@eniac871 could you please help looking into this
I have a PR to fix this issue.
Describe the bug Set a node (for example, a command node) in a pipeline job with managed identity configuration, but the job was recognized as user identity configuration, also, the raw json of the job showed that the credential passthrough as true. To Reproduce Steps to reproduce the behavior: