Open jghal opened 3 years ago
Additionally, since our AWX is inside the subscription, we enable the keyvault service endpoint in the subnet, and have NACLs enabled to restrict keyvault access to internal connections. So using the public routed https://<vault_name>.vault.azure.net
won't work for us either.
I second this one
ISSUE TYPE
SUMMARY
We deploy AWX inside subscriptions on a VM with a Managed Service Identity, so that we don't have to configure service principal client IDs and secrets (along with the necessary rotation policies and process). We would like to use the Azure Keyvault credential plugin, as an input source for other credentials. However it appears that this can only be used with statically configured client ID and secret. Putting in dummy values for client ID and secret products an authentication error.
https://docs.microsoft.com/en-us/azure/developer/python/azure-sdk-authenticate#authenticate-with-defaultazurecredential