Authenticate with Your Cloud Provider
To start using any feature of Cloud Manager, you must authenticate with your cloud provider credentials. This ensures a secure connection and access to your cloud infrastructure.
Note
Thinfinity Workspace is a multi-cloud solution, hence the process of registering credentials in Thinfinity Cloud Manager varies slightly depending on the cloud provider you are using. We currently support IONOS, Azure, AWS, GCP, OCI, Proxmox, HyperV, VMware, and Verge.IO and we are working on adding new providers. While each provider has their specific requirements and steps for integration, in this series of tutorials we focus on IONOS examples.
Configure Credentials
In Cloud Manager home screen, go to Credentials, and fill in the required fields.
IONOS
Use Token Authentication
Set to true to enable authentication via token. An additional Token field will become available.
Username/Email
This is the default authentication method for the IONOS cloud services provider. Enter the configured username or email address.
Password
Enter the configured password.
Contract Number
Enter the unique identifier utilized to differentiate among various user accounts.
Please find below the fields that must be completed for the rest of the cloud services provider.
Oracle Cloud
Use Instance Principal
Set to true to allow a computer instance to authenticate and make API calls to other OCI services securely. Enabling this option will hide all remaining fields except for Region.
Tenancy Id
Enter the provided Tenancy ID.
User Id
Enter the provided User ID.
Private Key (.PEM file)
Upload your custom .PEM file.
Fingerprint
A unique identifier (MD5 hash) of the API Signing Key uploaded to your OCI user profile. It is used to identify which public key OCI should use to verify your programmatic requests.
Region
Choose the region from the dropdown menu.
Microsoft Azure
Subscription
Enter the subscription ID - a unique identifier that acts as a logical container for your Azure resources and is a key field when configuring Microsoft Azure credentials.
Client ID
Enter the client ID - the unique identifier assigned upon registration of an application within Microsoft Entra ID (Azure Active Directory).
Client Secret
Enter the client secret - the unique string credential used by the application as an authentication factor, serving to verify its identity during access token issuance requests.
Tenant ID
Enter the tenant ID - the unique identifier for your organization's specific instance of the Microsoft Entra ID (formerly Azure Active Directory) service.
AWS
Access Key
Enter the unique identifier used to authorize user access.
Secret Key
Enter the private key utilized for digitally signing API requests to AWS services. Note: This key is displayed only once at the time of creation within the AWS Management Console and must be securely stored and kept confidential.
Region
Choose the region from the dropdown menu.
GCP
Service JSON file
Upload the JSON file for GCP service account credentials, typically contains fields used for authenticating an application or service with Google APIs.
VMware vSphere
vCenter Host
Enter the IP address or fully qualified domain name of the target system you want to connect to or manage.
vCenter Port
In most management or backup applications, the default communication port is 443. To use an alternative port, specify the desired port number in the Port field if your vCenter server is configured to operate on a non-standard port.
User/Password
Use the configured username and password
Allow Unverified SSL
Enabling this option bypasses critical security checks.
Hyper-V
Host
Enter the FQDN or IP Address of the Hyper-V server or cluster you wish to manage.
User/Password
Enter the configured username and password.
Proxmox
Proxmox Api Url
Use the complete HTTPS URL of your Proxmox server. It typically follows this format: https://your-proxmox-server-ip:8006/api2/json/.
User/Password
Use the configured username and password.
Disable TLS verification
Disabling TLS verification lowers security and should only be used on fully trusted, isolated networks.
VergeIO
Server
Enter the FQDN or IP address of the VergeIO server or cluster you wish to manage.
Allow Insecure SSL
Enabling this option bypasses critical security checks.
User OIDC Authentication
Enable OAuth 2.0 authentication via OIDC. Required parameters include: - OIDC Issuer URL - OIDC Client ID - OIDC Client Secret - OIDC Scope - OIDC Access Token - OIDC Refresh Token Check the official docs for more information.
Username/Password
Use the configured username and password.
Click Save, when you finish. Your credentials are available now in the Credentials tab. This will allow you to manage existing VMs as well as the creation of new instances.
Last updated