Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set-AzureRmApiManagementUser throws ValidationError when State is not specified #2622

Closed
solankisamir opened this issue Jul 15, 2016 · 2 comments
Labels
API Management Service Attention This issue is responsible by Azure service team.

Comments

@solankisamir
Copy link
Member

When Set-AzureRmApiManagementUser is execute without State, it throws error ValidationError, as the UserState that is passed is 0, which is an Invalid User State.

solankisamir added a commit to solankisamir/azure-powershell that referenced this issue Sep 20, 2016
- Upgrade ApiMAnagement nuget to 3.0.0-preview
- Added test for WSDL Importing Exporting
- Added test for Swagger Importing Exporting
- Added test for ARM VNET both with External and Internal VIP
- Fixed powershell Issue on ApiManagement
Azure#2622 - Retrieve State
from Server
- Fixed Powershell Issue on ApiManagement
Azure#2606 - Use Patch
- Regenerated all Session Records
- Deprecated cmdlet ManageVirtualNetwork
- Refactored RP tests for proper cleanup in Finally block
solankisamir added a commit to solankisamir/azure-powershell that referenced this issue Sep 20, 2016
- Upgrade ApiMAnagement nuget to 3.0.0-preview
- Added test for WSDL Importing Exporting
- Added test for Swagger Importing Exporting
- Added test for ARM VNET both with External and Internal VIP
- Fixed powershell Issue on ApiManagement
Azure#2622 - Retrieve State
from Server
- Fixed Powershell Issue on ApiManagement
Azure#2606 - Use Patch
- Regenerated all Session Records
- Deprecated cmdlet ManageVirtualNetwork
- Refactored RP tests for proper cleanup in Finally block
solankisamir added a commit to solankisamir/azure-powershell that referenced this issue Sep 21, 2016
- Upgrade ApiMAnagement nuget to 3.0.0-preview
- Added test for WSDL Importing Exporting
- Added test for Swagger Importing Exporting
- Added test for ARM VNET both with External and Internal VIP
- Fixed powershell Issue on ApiManagement
Azure#2622 - Retrieve State
from Server
- Fixed Powershell Issue on ApiManagement
Azure#2606 - Use Patch
- Regenerated all Session Records
- Deprecated cmdlet ManageVirtualNetwork
- Refactored RP tests for proper cleanup in Finally block
@solankisamir
Copy link
Member Author

The powershell release https://www.powershellgallery.com/packages/AzureRM/3.0.0 contains the fix.

solankisamir added a commit to solankisamir/azure-powershell that referenced this issue Oct 12, 2016
- Upgrade ApiMAnagement nuget to 3.0.0-preview
- Added test for WSDL Importing Exporting
- Added test for Swagger Importing Exporting
- Added test for ARM VNET both with External and Internal VIP
- Fixed powershell Issue on ApiManagement
Azure#2622 - Retrieve State
from Server
- Fixed Powershell Issue on ApiManagement
Azure#2606 - Use Patch
- Regenerated all Session Records
- Deprecated cmdlet ManageVirtualNetwork
- Refactored RP tests for proper cleanup in Finally block
@thomasddn
Copy link

I believe this issue has been reintroduced. Currently using AzureRM v5.0.1 and I can't update a user's password without passing the state.

The error message:

Set-AzureRmApiManagementUser : ValidationError: One or more fields contain incorrect values:
At line:1 char:1
  Set-AzureRmApiManagementUser -Context $apimContext -UserId "test" -Pa ...
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    CategoryInfo          : CloseError: (:) [Set-AzureRmApiManagementUser], CloudException
    FullyQualifiedErrorId : Microsoft.Azure.Commands.ApiManagement.ServiceManagement.Commands.SetAzureApiManagementUser

@bsiegel bsiegel added the Service Attention This issue is responsible by Azure service team. label Sep 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Management Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants