How-To Integrate a 3rd Party Tool - Part 3: Resource Handler Credentials

Overview

In some cases, the integration you are looking for is some additional functionality from a Resource Handler (RH) / Cloud Platform that already has stored credentials in CloudBolt (CB). For this use case, we can look up and re-use the credentials already stored for the resource handler.

This article will only cover examples for AWS, Azure and vCenter

You can also invoke a session using our api wrappers. This will be discussed in a future article of this series.

Considerations

Account Permissions:

  • If you are allowed to have a single account for the RH and the new integration, it is recommended that you do so and update the permissions for all use cases. This reduces account and Connection Info splay.

  • If you are not allowed to re-use accounts, this use case is not for you and you should consider creating a Connection Info.

AWS Credentials Procedure

from resourcehandlers.vmware.models import AWSHandler

rh = AWSHandler.get(name="AWS")

# key
rh.serviceaccount

# secret
rh.servicepasswd

Azure Credentials Procedure

from resourcehandlers.vmware.models import AzureARMHandler

rh = AzureARMHandler.get(name="Azure")

# Subscription ID
rh.serviceaccount

# Client Secret
rh.secret

# Client ID
rh.client_id

# Tenant ID
rh.azure_tenant_id

vCenter Credentials Procedure

from resourcehandlers.vmware.models import VsphereResourceHandler

rh = VsphereResourceHandler.get(name="vCenter")

# username
rh.serviceaccount

# password
rh.servicepasswd

Additional information

Include links to outside source articles or reference material if applicable

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.