Skip to main content

Authentication Configuration

This guide explains how to configure both user and agent authentication in zymtrace.

Authentication protects profiling data and restricts access to authorized users.

Quick Start​

Use this minimal auth section in your custom-values.yaml to enable local authentication. All other fields will fall back to the defaults defined in values.yaml.

Artifact Hub: zymtrace backend

Helm Chart Source

The Helm chart source code is available on GitHub: zystem-io/zymtrace-charts

custom-values.yaml
auth:
# Enable built-in local authentication
type: "local"

# Admin user for first login
admin:
email: admin@example.com
password: "your-secure-password"
roles:
- "System Admin"

# Optional: enable service tokens for agents/CLI
serviceToken:
enabled: true

Refer to the local authentication guide to create a pair of keys when deploying to production.

Authentication Methods​

zymtrace supports several authentication methods:

Auth TypeDescriptionUse Case
noneNo authentication requiredDevelopment, testing, trusted networks
localBuilt-in authentication with username/passwordSelf-hosted deployments, on-premises
oidcOpenID Connect integrationEnterprise SSO, Google, Okta, Azure AD
basicHTTP Basic authenticationSimple API access, service-to-service
Production Recommendation

For production environments, we recommend using oidc for enterprise SSO integration or local for built-in authentication. Always use HTTPS/TLS when authentication is enabled.

Common Configuration​

Admin User Configuration​

Regardless of authentication type, an admin user is created automatically and has full access.

auth:
admin:
email: admin@example.com
password: admin
roles:
- "System Admin"
Security

Change default admin credentials immediately after deployment.

Service Token Configuration​

Service tokens enable programmatic access for agents, CLI tools, and automation.

auth:
serviceToken:
enabled: true # Enable service token generation and authentication
When to Enable

Enable when:

  • Using CI/CD pipelines
  • Running agents outside trusted networks
  • Building custom API integrations
Security

Running the agent with -disable-tls exposes the token publicly.