Skip to content
New issue

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

Natively import .pfx (PKCS #12) certificates #549

Open
gooseleggs opened this issue Jul 15, 2022 · 0 comments
Open

Natively import .pfx (PKCS #12) certificates #549

gooseleggs opened this issue Jul 15, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@gooseleggs
Copy link

When creating certificates with a third party CA, in this case MS Certificate Services, to export the certificate you need to export it in PKCS#12 format. However, to import the certificate into Ziti, you need to provide the key and cert file as two separate files. It would be nice to be able to import a .pfx file directly and specify either the password with a command line option, or prompt for it if it is missing.

This will mean that the certificate will remain 'safe' while in transit between Windows CA and client, ie a safe passage from export of the cert from the CA and ziti client import.

It will also mean that you dont need to install openssl to split the cert up and take the password off the key file. All of which is extra work for users using the front end.

@dovholuknf dovholuknf added the enhancement New feature or request label Jul 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants