06-25-2019 07:57 AM
We are using the InfoBlox plugin (4.4) with vRA 7.4 with great success. However, we see that the API authentication is driven by a connection that is established when a blueprint deployment is executed. The endpoint connection credentials are passed to vRO, by vRA, only at deployment time. The connection is then short-lived.
What is the recommended way to store credentials and create connections for XaaS and vRO-scheduled workflows using the InfoBlox plugin/API?
My initial thought is to use a vRO configuration element to store the username/password but was hoping there was a more elegant solution envisioned by the plugin designers.
06-25-2019 09:25 AM
The endpoint connection to NIOS for the plugin is stored in the vRO cache whenever the allocate or release workflows are called. It has been recognized that this is not always the most ideal way for the plugin to operate, so this is under review and future updates to the plugin may work differently in this regard.
If you are attempting to create your own (custom) workflows, you can use the allocate and release workflows as examples for how these connections are built. And ideally, any future updates to the plugin will eliminate the need for this at all.
06-25-2019 09:40 AM
Thank you for the response. Indeed we have inspected the allocate and release workflows. The thing is that they receive the username/password as a special object type from vRA during deployments. We have been unable to find any way to retrieve the username/password from vRA other than through the plugin running those specific workflows.
Instead I guess we'd have to store the username/password somewhere in vRO (such as a configuration element).