Azure / azure-cli

Azure Command-Line Interface
MIT License
4.03k stars 3.01k forks source link

`az ad sp credential delete` does not delete SAML signing cert #24635

Open tagur87 opened 2 years ago

tagur87 commented 2 years ago

This is autogenerated. Please review and update as needed.

Describe the bug

When running az ad sp credential delete --cert --id xxxx --key-id xxxx to delete an inactive SAML signing certificate, the command succeeds, but there are no changes in the API or the GUI.

Command Name az ad sp credential delete

Errors:

None

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Expected Behavior

Expect the inactive certificate with the key-id sent through the delete command should be removed.

Environment Summary

Linux-5.10.16.3-microsoft-standard-WSL2-x86_64-with-glibc2.35, Ubuntu 20.04.5 LTS
Python 3.10.8
Installer: HOMEBREW

azure-cli 2.42.0

Additional Context

yonzhan commented 2 years ago

@jiasli for awareness

jiasli commented 1 year ago

Azure CLI currently has no support for SAML-based AAD apps (#7579), so this use case is not supported either.


Even so, I did some investigation and can provide some further information.

az ad sp credential delete command calls the Update servicePrincipal Microsoft Graph API to delete certificate credential from the keyCredentials property of the service principal object. It raises an error if the key_id doesn't exist in keyCredentials:

https://github.com/Azure/azure-cli/blob/00fe3e551fbc574abfd3e099e8e15e6ecb623a06/src/azure-cli/azure/cli/command_modules/role/custom.py#L1777-L1790

You may run az ad sp credential delete with --debug to verify how it works and which APIs are invoked.

Therefore, it is very likely to be a Microsoft Graph API issue:

  1. The SAML signing certificate can be retrieved under the keyCredentials property of the service principal object.
  2. But it cannot be removed by first removing it from the keyCredentials property then calling Update servicePrincipal API.

I would suggest contacting Microsoft Graph support for further investigation.