Password hard coded to blank when authenticating SP using a certificate

[kkizer]

In the "Spn login with pfx certificate" scenario, you can specify the path to the certificate using the --client-certificate argument. However, you cannot specify the password used in the PFX to encrypt the private key. A new parameter is needed to allow the password and can default to blank (to keep the current behavior).

[NaeemH]

The --client-certificate-password flag requested here is already implemented — it is registered in AddFlags, read from AAD_SERVICE_PRINCIPAL_CLIENT_CERTIFICATE_PASSWORD / AZURE_CLIENT_CERTIFICATE_PASSWORD in UpdateFromEnv, propagated through the kubeconfig converter, and passed to readCertificate/decodePkcs12 for PFX login. PR #793 adds unit tests that lock in the password-protected PFX decode path (correct vs. wrong password). This issue looks safe to close.

[NaeemH]

The --client-certificate-password flag requested here is already implemented — it's registered in AddFlags, read from AAD_SERVICE_PRINCIPAL_CLIENT_CERTIFICATE_PASSWORD / AZURE_CLIENT_CERTIFICATE_PASSWORD in UpdateFromEnv, propagated through the kubeconfig converter, and passed to readCertificate/decodePkcs12 for PFX login. PR #793 adds unit tests that lock in the password-protected PFX decode path (correct vs. wrong password). This issue looks safe to close.