Credential Providers
This section covers Credential Providers in Aembit, which you can use to provide access credentials to Client Workloads so they can access Server Workloads securely.
The following pages provide information about different Credential Provider types and how to configure them:
- Aembit Access Token
- API Key
- AWS Secrets Manager
- AWS Security Token Service Federation
- AWS SigV4
- Azure Entra Workload Identity Federation
- Azure Key Vault
- Claude Workload Identity Federation
- Google GCP Workload Identity Federation
- JSON Web Token (JWT)
- JWT-SVID Token
- Managed GitLab Account
- MCP Enterprise Managed Access Token
- MCP User-Based Access Token
- OAuth 2.0 Authorization Code
- OAuth 2.0 Client Credentials
- OIDC ID Token
- OpenAI API Workload Identity Federation
- Username Password
- Vault Client Token
- X.509-SVID
About Credential Providers
Section titled “About Credential Providers”- About JWT-SVID Tokens
- About MCP Enterprise Managed Access Tokens
- About MCP User-Based Access Tokens
- About OIDC ID Tokens
- About X.509-SVID
Advanced options
Section titled “Advanced options”- Private Network Access
- Multiple Credential Providers
- HashiCorp Vault Dynamic Claims
- Dynamic Claims
- Multiple Credential Providers Terraform