tag:blogger.com,1999:blog-7690936181217466579.post4011809966504340998..comments2023-12-07T21:21:46.914-08:00Comments on StorageGumbo: Starting vRO Workflows with Log Insight WebhooksJohn Diashttp://www.blogger.com/profile/14840017501934390262noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7690936181217466579.post-52658850588073701432017-07-19T14:28:20.328-07:002017-07-19T14:28:20.328-07:00Will do, thanks.Will do, thanks.Unknownhttps://www.blogger.com/profile/01247197786343097809noreply@blogger.comtag:blogger.com,1999:blog-7690936181217466579.post-91319494183270809872017-07-19T08:27:30.588-07:002017-07-19T08:27:30.588-07:00Juan, can you open an issue on the github repo for...Juan, can you open an issue on the github repo for webhook shims? This will allow others to respond and we can track this. Thanks!John Diashttps://www.blogger.com/profile/14840017501934390262noreply@blogger.comtag:blogger.com,1999:blog-7690936181217466579.post-55401835434163253192017-07-18T09:53:52.362-07:002017-07-18T09:53:52.362-07:00Hi John,
I followed the procedure on https://blog...Hi John,<br /><br />I followed the procedure on https://blogs.vmware.com/management/2017/02/self-healing-data-center-part-4.html but I keep getting a 401 response every time the shim sends the request to vRO:<br /><br />2017-07-17 20:39:39,623 INFO URL=https://10.65.65.110:8281/vco/api/workflows/891596b4-c5a5-4bf2-ac26-bbb20090ae15/executions<br />2017-07-17 20:39:39,624 INFO Headers={'Content-type': 'application/json'}<br />2017-07-17 20:39:39,624 INFO Body={"parameters": [{"name": "alertId", "scope": "local", "type": "string", "value": {"string": {"value": "6f2d0b2a-e566-4d7b-bdc6-602d9b31c37b"}}}]}<br />2017-07-17 20:39:39,624 INFO Check=False<br />2017-07-17 20:39:39,628 DEBUG Starting new HTTPS connection (1): 10.65.65.110<br />/root/webhook-shims/venv-webhookshims/lib/python2.7/site-packages/urllib3/connectionpool.py:852: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings<br /> InsecureRequestWarning)<br />2017-07-17 20:39:39,658 DEBUG https://10.65.65.110:8281 "POST /vco/api/workflows/891596b4-c5a5-4bf2-ac26-bbb20090ae15/executions HTTP/1.1" 401 1154<br />2017-07-17 20:39:39,660 INFO 10.66.65.227 - - [17/Jul/2017 20:39:39] "POST /endpoint/vro/891596b4-c5a5-4bf2-ac26-bbb20090ae15/6f2d0b2a-e566-4d7b-bdc6-602d9b31c37b HTTP/1.1" 401 -<br /><br /><br />I found this information as well on the vRO Swagger:<br /><br />"Single Sign-On Authentication<br />If Orchestrator is configured with the vCenter Single Sign-On (SSO) server, you need a principal holder-of-key (HoK) token to access system objects in Orchestrator through the REST API.<br />The HoK token is passed as a request Authorization header element. The value must be gzip, base64<br />encoded string.<br /><br />To be able to test the service bellow you need to enable basic authentication over sso.<br />This happens by adding the following property to vmo.properties configuration file:<br /><br />com.vmware.o11n.sso.basic-authentication.enabled = true "<br /><br />I added the line to the vRO config and restarted the appliance, now I can send requests using Swagger using the syntax user@domain, but still no luck with the shim.<br /><br />In your example here the syntax is administrator@vsphere.local, same as I have it on the netrc file. Are you aware or any other requirements?, do I need a HoK token to make this work?<br /><br />Thank you,<br /><br /><br />Juan.Unknownhttps://www.blogger.com/profile/01247197786343097809noreply@blogger.com