Open zosocanuck opened 3 years ago
@zosocanuck - This issue was resolved in https://github.com/Indellient/chef-habitat-venafi-helper/pull/2 and the docs updated accordingly in https://github.com/Indellient/chef-habitat-venafi-helper/pull/4.
The issue is actually with the configuration structure within the venafi-helper component. Once that is corrected according to the new documentation, you should no longer experience the issue.
Made the necessary changes to the user configuration file and now seeing this error:
venafi-tomcat-demo.default(SR): Waiting for service binds... venafi-helper.default(O): vCert: 2021/02/22 23:48:11 Successfully read zone configuration for DevOps\Kubernetes venafi-helper.default(O): vCert: 2021/02/22 23:48:11 Successfully created request for habitat.selab.venafi.com venafi-helper.default(O): vCert: 2021/02/22 23:48:11 Getting guid for object DN \VED\Policy\DevOps\Kubernetes\habitat.selab.venafi.com venafi-helper.default(O): vCert: 2021/02/22 23:48:11 object with DN \VED\Policy\DevOps\Kubernetes\habitat.selab.venafi.com doesn't exist venafi-helper.default(O): vCert: 2021/02/22 23:48:11 Unexpected status code on TPP Certificate Request. venafi-helper.default(O): Status: venafi-helper.default(O): 400 Bad Request. venafi-helper.default(O): Body: venafi-helper.default(O): {"Error":"Unable to parse input document."} hab-launch(SV): Child for service 'venafi-helper.default' with PID 1160 exited with code exit code: 1
@zosocanuck - In the later versions of vcert, username/password authentication was no longer supported. Support for token based authentication has been added in https://github.com/Indellient/chef-habitat-venafi-helper/pull/5 to resolve and the docs updated accordingly.
After following the steps to run the tomcat demo I get the following errors from the Habitat logs:
I am running the latest Habitat on CentOS 7 along with the latest indellient code.