Skip to main content
For the steps to change these secrets, start at Planning for Production.

Tyk Gateway

Tyk Dashboard

Admin User From the Setup Script

The script /opt/tyk-dashboard/install/bootstrap.sh creates a Tyk Dashboard user with a fixed password, which is the same in every installation. If you use this script, change the password of that user after you log in for the first time. The script calls the Tyk Dashboard Admin API with the sample value of admin_secret. If you change admin_secret before you run the script, edit the script first, or create the first user in the Tyk Dashboard UI.

Tyk MDCB

Tyk MDCB does not ship sample secrets. Set these values before you go to production.

Tyk Pump

Tyk Pump does not ship sample secrets. Set the credentials for each data store that it uses.

Tyk Developer Portal

Tyk AI Studio

The Linux packages install /etc/default/tyk-ai-studio with placeholder values. The AI Studio Helm chart leaves the same values empty. Some example .env files in the AI Studio repository contain sample encryption keys of exactly 32 characters. AI Studio and Edge Gateways accept these values. Do not copy them into a deployment. The AI Studio Helm chart also has these defaults: For the AI Studio settings, see AI Studio Environment Variables.

Tyk Helm Charts

The Tyk Helm charts do not generate secrets, with one exception: the Tyk Dashboard admin password, when you set it to an empty value. Set these values, or supply them from Kubernetes Secrets.

Supply Helm Values From Kubernetes Secrets

Create the Kubernetes Secret first, then refer to it in your values file. When you refer to a Secret, the chart ignores the plain-text value. For example, to supply the API secret and the admin secret:
For more detail, see the chart pages: tyk-stack, tyk-control-plane, tyk-data-plane and tyk-oss.

Change the API Secret Safely

When security.private_certificate_encoding_secret is empty, Tyk Gateway encrypts the private keys in the Tyk Certificate Store with secret, and Tyk Dashboard uses tyk_api_config.secret. If you change the API secret, Tyk can no longer read the private keys that it stored before. To change the API secret on an existing installation:
  1. Set security.private_certificate_encoding_secret to the current value of secret in Tyk Gateway, Tyk Dashboard and Tyk MDCB.
  2. Restart the components.
  3. Change secret in Tyk Gateway and tyk_api_config.secret in Tyk Dashboard to the new value.
  4. Restart the components.
On a new installation, set security.private_certificate_encoding_secret to its own random value before you add certificates.