We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As per
release/utils/release.bash
Lines 79 to 81 in 7a03f98
pfx
However, this comment was made in 2020. We are 2023, and as per https://learn.microsoft.com/en-us/azure/key-vault/certificates/tutorial-import-certificate?tabs=azure-portal, password for pfxcertificate seems supported.
As an additional layer of security, we should be able to use a password (instead of converting pfx to pem for adding one).
Discovered while working on jenkins-infra/helpdesk#3323
The text was updated successfully, but these errors were encountered:
You might want to read the docs a bit closer ^.^
Once the certificate file is successfully imported, key vault will remove that password.
Sorry, something went wrong.
🤦 correct, thanks for pointing it out 😅
Gotta close the issue then 👍
No branches or pull requests
As per
release/utils/release.bash
Lines 79 to 81 in 7a03f98
pfx
file does not have a password.However, this comment was made in 2020. We are 2023, and as per https://learn.microsoft.com/en-us/azure/key-vault/certificates/tutorial-import-certificate?tabs=azure-portal, password for
pfx
certificate seems supported.As an additional layer of security, we should be able to use a password (instead of converting pfx to pem for adding one).
Discovered while working on jenkins-infra/helpdesk#3323
The text was updated successfully, but these errors were encountered: