storage: API incorrectly returns an error when User Assigned Identities are specified

[tombuildsstuff]

Service: Storage
API Version 2021-04-01

The Storage API supports Managed Identity however returns an error when an empty list of User Assigned Identities is provided when specifying a a System Assigned Identity.

Since a System Assigned Identity doesn't use any of the User Assigned Identities and there are none specified, these should be being ignored - however instead the API returns:

Failed to perform resource identity operation. Status: 'BadRequest'. Response: '{"error":{"code":"BadRequest","message":"The request format was unexpected, a non-UserAssigned identity type should not contain: userAssignedIdentities"}}

Can the Storage API be updated to fix this bug?

Thanks!

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

Issue Details

---

Service: Storage
API Version 2021-04-01

The Storage API supports Managed Identity however returns an error when an empty list of User Assigned Identities is provided when specifying a a System Assigned Identity.

Since a System Assigned Identity doesn't use any of the User Assigned Identities and there are none specified, these should be being ignored - however instead the API returns:

Failed to perform resource identity operation. Status: 'BadRequest'. Response: '{"error":{"code":"BadRequest","message":"The request format was unexpected, a non-UserAssigned identity type should not contain: userAssignedIdentities"}}

Can the Storage API be updated to fix this bug?

Thanks!

Author:	tombuildsstuff
Assignees:	-
Labels:	question, Storage, Service Attention, customer-reported, needs-triage
Milestone:	-

[blueww]

@HimanshuChhabra
Would you please help to look at the server error?

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @josephkwchan, @jennyhunter-msft.

Issue Details

---

Service: Storage
API Version 2021-04-01

The Storage API supports Managed Identity however returns an error when an empty list of User Assigned Identities is provided when specifying a a System Assigned Identity.

Since a System Assigned Identity doesn't use any of the User Assigned Identities and there are none specified, these should be being ignored - however instead the API returns:

Failed to perform resource identity operation. Status: 'BadRequest'. Response: '{"error":{"code":"BadRequest","message":"The request format was unexpected, a non-UserAssigned identity type should not contain: userAssignedIdentities"}}

Can the Storage API be updated to fix this bug?

Thanks!

Author:	tombuildsstuff
Assignees:	HimanshuChhabra
Labels:	question, Storage, ARM, Service Attention, customer-reported
Milestone:	-

[blueww]

Add label "ARM" and remove "Storage", since the error is not coming from SRP, It is being returned by the either ARM/MSI Service.

[tombuildsstuff]

@blueww any idea of a timeframe to fix this? So far this has taken 8 months to be routed to the right team.

[jennyhunter-msft]

It looks like the error response is not contained within ARM's repository, which means that it might be something related to Managed Identities - this error response should be handled by them.

I would assume this error is occurring by-design, because an improper input is being passed in, but that would also depend on the API contract specified; either way, we would need some correlation identifier to guarantee that an outgoing request is being made from ARM and the error response is just being propagated.

[blueww]

@tombuildsstuff
As I get from ARM/MSI team, this validation is by design.
Server will return error if the userAssigendIdentity dictionary is empty.

[tombuildsstuff]

@blueww this isn't the case for other Resource Manager API's, so why is Storage behaving differently here?

[blueww]

@tombuildsstuff

For "this isn't the case for other Resource Manager API's", could you give the details?