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

https with .pfx file configuration is ignored #1061

Closed
yogevyuval opened this issue Oct 7, 2018 · 1 comment
Closed

https with .pfx file configuration is ignored #1061

yogevyuval opened this issue Oct 7, 2018 · 1 comment

Comments

@yogevyuval
Copy link
Contributor

#349 for some reason introduces a regression of a feature that seems to once work. https.pfx option is currently being ignored because of the following if statement:

if (!config.https || !config.https.key || !config.https.cert || !config.https.ca)

which was committed instead of the code that once worked:

if (!config.https || !((config.https.key && config.https.cert && config.https.ca) || config.https.pfx))

Currently we only check if there is key, cert and ca options and if not a warning is shown and the process exits.

To Reproduce
Steps to reproduce the behavior:

  1. Create a PFX file and add it according to the documentation
  2. Run verdaccio
  3. An error is shown:

'You have enabled HTTPS and need to specify either ',
' "https.key", "https.cert" and "https.ca" or ',
' "https.pfx" and optionally "https.passphrase" ',
'to run https server'

Expected behavior
We should check if the configuration has a key, cert and ca OR a pfx file.

@juanpicado juanpicado added this to the 3.x.x milestone Oct 7, 2018
juanpicado pushed a commit that referenced this issue Oct 7, 2018
* Don't exit if using https and pfx is enabled

* Fix indentation
@lock
Copy link

lock bot commented Apr 25, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot added the outdated label Apr 25, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants