-
Notifications
You must be signed in to change notification settings - Fork 693
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
Add support for PFX or PKCS12 encoded certificates #708
Conversation
c1bf840
to
8bf73f3
Compare
Linked PR is now merged 🎉 Want to merge in those changes and let me know when this is ready for review? |
Add support for PFX or PKCS12 encoded certificates
21d6859
to
028f5d4
Compare
I have rebased the changes based on the recent PR, @leerob you may please review the PR and let me know feedback/changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would love a test for this – maybe we can add that in follow-up building off #712.
Testing has now been added! |
Updated cli snapshot due to change in help test, using vitest -u option
@leerob I have updated the cli test snapshot with updated text. Can I start another PR for adding tests specific for PFX certs? This will help get this PR merged while I work on tests. Open to suggestions |
This PR adds additional work based on the excellent work in #706 for Typescript.
Added support for PFX or PKCS12 encoded certificates by auto detecting format using options passed for SSL. No additional parameter needed to detect. This continues the work in #508 that was in older JS format
For using PFX certificates use following parameters
--ssl-cert
This is the path to the PFX certificate--ssl-pass
(Optional) This is the path to the password for PFX certificate.Examples for PFX
For PEM (no change)
This PR should only be merged after #706.
CC: @leerob @gamemaker1