You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if there is an error in certificate parsing either in the facter or the HFT host manufacturing within the module, the errors are silently eaten and create unhelpful message(s) later down the line when the connection fails. Given that in most cases a problem will result in no certs parsed, we can error out early but we don't.
Summary
Currently, if there is an error in certificate parsing either in the facter or the HFT host manufacturing within the module, the errors are silently eaten and create unhelpful message(s) later down the line when the connection fails. Given that in most cases a problem will result in no certs parsed, we can error out early but we don't.
Dev info:
Steps to Reproduce
Steps to reproduce the behavior:
2 Setup clean Windows host ready (don't run agent yet)
ssl_certificateparamExpected Results
Well formed and descriptive errors that there's a problem parsing the certificate(s)
Actual Results (including error logs, if applicable)
Error about "certificate verification failure"
Reproducible
Version/Tag number
Tested on Puppet 6 and pre-3.0.0 version but this error would be visible on puppet 5 and any older version as well probably.
Environment setup
Puppet Master: Docker-compose, v6
Puppet Agent: Windows 2012r2 VM in VirtualBox
Conjur Master: Docker-compose, v5
Additional Information
N/A
The text was updated successfully, but these errors were encountered: