Skip to main content
Axottle stores sensitive data — ISP credentials, integration tokens, access keys — in a secure, disk-encrypted secret store, and this section describes how the storage works, why the master key is needed, and what kind of tokens are available.
For whom: Administrator and SRE. Required rights: panel administrator; access to server to configure master key.

Warehouse of secrets

Third-party service credentials (CDN provider accesses, DNS tokens, backup storage keys, monitoring integration tokens) are encrypted before being recorded in the database and never logged in the open form. Encryption is done by a modern authenticated encryption algorithm. One thing is important for documentation and operation: is protected by a single master key,, which you specify on the server.

Master key AXOTTLE_SECRET_KEY

The master key is set to the AXOTTLE_SECRET_KEY environment variable on the panel server.
In production , must specify a strong random key. If the key is not specified, an insecure default value is used for development - it is unacceptable in a combat environment.
Generate a secure key:
Set it in the panel environment file (/etc/axottle/axottle.env) and restart the service. The order of safe variable change is Configuration.
Changing the master key makes previously stored secrets unreadable. There is no built-in master key rotation tool yet. If the key needs to be changed, after the shift, you will need to re-enter all the credentials of the providers and integrations. Plan this as a serviced operation.
The master key is used not only by the secret storage, but also to encrypt backups (when it’s turned on). Part of the functions (monitoring integrations, providers) won’t run without a predetermined key and will report it directly.

Service tokens

Some transactions use separate utility tokens. Save the token shown immediately after creation: you can’t re-watch it completely.
When you create a token, the panel displays a warning, “Save this token, it won’t be shown again.” Copy it immediately to a secure location. The lists display only a short prefix by which the token can be recognized, but not restored.
Read more about Node Registration Tokens – Node Registration.

Handling secrets

  • Consider any token issued a full-fledged secret: keep secrets in the manager, do not commit in the repository, do not send in open channels.
  • Recall tokens that are no longer needed or may have been compromised.
  • To access hosting providers, use dedicated keys with the minimum necessary rights.

Verification

AXOTTLE_SECRET_KEY is set with a strong value (not a default value), the service starts without errors about the unavailability of the key, and the ISP connection / integration test is successful.

Rollback

  • Compromised token: revoke it (for integration-token – deletion, for enrollment/agent – recall or re-registration of the node) and, if necessary, release a new one.
  • Provider credentials: delete them in the appropriate section - the entry in the secret repository is deleted.