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
Earlier discussed in #423, but asked to create a separate issue for it.
Currently when setting up any Chef Automate related features and/or any feature that requires another service, in addition to the Chef Server, the client doesn't handle the other server using self-signed SSL certificates -- and forces the user to run knife ssl fetch on each node being setup. A far from delightful experience.
The text was updated successfully, but these errors were encountered:
Earlier discussed in #423, but asked to create a separate issue for it.
Currently when setting up any Chef Automate related features and/or any feature that requires another service, in addition to the Chef Server, the client doesn't handle the other server using self-signed SSL certificates -- and forces the user to run
knife ssl fetch
on each node being setup. A far from delightful experience.The text was updated successfully, but these errors were encountered: