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.
Generate a secure key:
/etc/axottle/axottle.env) and restart the service. The order of safe variable change is Configuration.
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.
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.
