Getting Started
Table of Contents
Expand all | Collapse all
-
- Activate Next-Generation Trust Security
-
-
- Configure Akamai Connection
- Configure AWS Connection
- Configure Azure Key Vault Connection
-
- Workload Identity Federation Authentication
- Workload Identity Federation - Azure Identity Provider Authentication
- Next-Gen Trust Security Generated Key Authentication
- User Permissions
- Workload Identity Federation Authentication
- Next-Gen Trust Security Generated Key Authentication
- User Permissions
- Supported OIDC Claims
-
-
-
- Add AWS Public CA
- Add AWS Private CA
- Add DigiCert One Certificate Authority
- Add Entrust
- Add GlobalSign Atlas
- Add GlobalSign MSSL
- Add GoDaddy
- Add Google CAS (GCAS)
- Add a HID PKIaaS CA
- Add Certificate Manager - Self-Hosted
- Set Up an OpenSSL Certificate Authority Connector
- Create a Sectigo Certificate Manager Certificate Authority
- Add SSL.com
- Add Zero Touch PKI
-
- Example: Create a Custom CA Connector Using the CA Connector Framework
- Creating an Entrust CA Gateway Connector
- Creating a HashiCorp Vault CA Connector
- Creating a SecureW2 Connector
- Creating a SwissSign Connector
- Creating a Tucows OpenSRS Connector
- Working with Custom CA Connectors in the Certificate Authorities Inventory
- Set Up Certificate Expiration Notifications
- Using a Custom DNS Provider
- CNAME Delegation for Domain Validation
- About Authorized Domains
-
- Getting Started with Next-Gen CA
- Adding Root CAs
- Adding Issuing CAs
- Agentic Plugins for Next-Gen CA
- Downloading Root CA Certificates
- Decommissioning CAs
- Viewing Your PKI
- Viewing CA Details
- CA Configuration Limits
- Default CAs by Configuration Tier
- About the PKI Hierarchy
- About Configuration Tiers
- About Certificate Issuance and Revocation
- About Post-Quantum Certificates
- About Subordinate CA Providers
- Add Subordinate CA Providers
- About Issuer Configurations
- Issuer Certificates Page
-
-
- 47-Day Validity Readiness TLS Certificates
- About the Certificate Inventory
- Managing Certificate Lifecycle Settings
- Reissuing Certificates in Next-Gen Trust Security
- Duplicating DigiCert Certificates
- Downloading Certificates, Certificate Chains, and Keystores
- Retiring, Recovering, and Deleting Certificates
- Finding Certificates in the Certificate Inventory
- Importing Certificates from DigiCert
- Importing Certificates from EJBCA
- Importing Certificates from GlobalSign Atlas
- Importing Certificates from GlobalSign MSSL
-
- Create a Workload Identity Management or Discovery Agent Built-in Account
- Create an OCI Registry Built-in Account
- Create a Certificate Manager - Self-Hosted Built-in Account
- Create a Scanafi Built-in Account
- Toggling a Built-in Account On or Off
- Editing Built-in Accounts
- Deleting Existing Built-in Accounts
- Renew Existing Built-in Accounts
- Licensing PKI
- Troubleshooting
Getting Started
To get a VSatellite connected to your Next-Gen Trust Security account, you'll need to download and run a binary setup utility on a Linux server within your target network.
Prerequisites
Before you install a VSatellite, carefully review these important prerequisites:
- You'll need root privilegesYou'll need permission to run commands with root privileges. The following options are available:
- Use sudoIf the sudo command is available on your target Linux machine, you can use it to install VSatellite.Alternative privilege elevation utilities, such as dzdo, are not supported and may result in installation failure.
- Use a root shellIf you are already logged in as the root user, you do not need the sudo command.In this case, you can omit sudo wherever it appears with vsatctl in the documentation.
Why are root privileges required?The vsatctl install command installs k3s in /usr/local/bin, which is owned by the root user.If you are installing VSatellite on RHEL, Oracle, or Rocky Linux, the vsatctl install command installs the k3s-selinux RPM package. Installing RPM packages requires root privileges.Other vsatctl subcommands connect to the VSatellite cluster and require access to credentials stored in /etc/rancher/k3s/k3s.yaml. This file is accessible only to the root user. - If you plan to install on Red Hat Enterprise Linux (RHEL), carefully review these special considerations.
- If you plan to use a proxy, note that TLS MITM is not supported as a proxy mechanism.
- The target computer where you plan to install VSatellites must not have any existing Kubernetes distributions installed or running. If present, uninstall them first to avoid conflicts during the VSatellite installation.
- Allowlist FQDNs rather than IP addresses to ensure connectivity between VSatellites and Next-Gen Trust Security. Learn more.
- Ensure that your target machine meets all system requirements.