az feedback auto-generates most of the information requested below, as of CLI version 2.0.62
Describe the bug
The following command fails, and should succeed:
» az ad app credential reset --id "$APP_ID" --append --credential-description 'a description here' --end-date '2299-12-31'
When present, application key identifier cannot be empty and can be at most 32 bytes.
Parameter name: applicationKeyIdentifierValue
To Reproduce
Run the above command against an application registration.
Expected behavior
It succeeds, creating a new credential.
Environment summary
brew
Additional context
It seems like this is also https://github.com/Azure/azure-docs-powershell-azuread/issues/296 ; that bug was closed without any meaningful resolution. It seems like az is mixing up the description with something else. The error emitted here is grade A bonkers: "can be at most 32 bytes" when the input text is less than 32 bytes? It seems like it is getting mixed up with an encryption key, or something, and isn't actually transmitting the provided value as a description.
The value itself is also fine: it is possible to go to the Portal & create a new credential with the description a description here without problems. Hence, this seems to be an azure-cli problem.
Describe the bug
The following command fails, and should succeed:
To Reproduce
Run the above command against an application registration.
Expected behavior
It succeeds, creating a new credential.
Environment summary
brewAdditional context
It seems like this is also https://github.com/Azure/azure-docs-powershell-azuread/issues/296 ; that bug was closed without any meaningful resolution. It seems like
azis mixing up the description with something else. The error emitted here is grade A bonkers: "can be at most 32 bytes" when the input text is less than 32 bytes? It seems like it is getting mixed up with an encryption key, or something, and isn't actually transmitting the provided value as a description.The value itself is also fine: it is possible to go to the Portal & create a new credential with the description
a description herewithout problems. Hence, this seems to be an azure-cli problem.