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
{{ message }}
This repository has been archived by the owner on May 10, 2018. It is now read-only.
Issue: Chef server can use certs, however current documentation does not provide any guidance for certs generated using Micorosoft cert authority. The issue is that certs are provided in a .PFX format, and chef server consumes them in a crt / pem + key format.
This mean, the .pfx needs to be converted to a consumable format using Openssl command which are a complete mystery to pretty much everyone.
Fix: (tested but not sure if it covers all of the possible scenarios with .pfx files). Please add below lines and general description of the problem to pages referencing configuring NGINX for chef server.
Note: These commands were executed with OpenSSL 1.0.1f 6 Jan 2014 which comes baked into chef-server 12.2.0-1
The text was updated successfully, but these errors were encountered:
vinyar
changed the title
no documentation on chef-server.rb page for cergs generated on windows
no documentation on chef-server.rb page for certs generated on windows
Oct 29, 2015
Sites:
https://docs.chef.io/config_rb_server.html
https://docs.chef.io/config_rb_server_optional_settings.html
https://docs.chef.io/server_security.html
Issue: Chef server can use certs, however current documentation does not provide any guidance for certs generated using Micorosoft cert authority. The issue is that certs are provided in a .PFX format, and chef server consumes them in a crt / pem + key format.
This mean, the .pfx needs to be converted to a consumable format using Openssl command which are a complete mystery to pretty much everyone.
Fix: (tested but not sure if it covers all of the possible scenarios with .pfx files). Please add below lines and general description of the problem to pages referencing configuring NGINX for chef server.
Note: These commands were executed with
OpenSSL 1.0.1f 6 Jan 2014
which comes baked into chef-server12.2.0-1
The text was updated successfully, but these errors were encountered: