Manage security and authorization
API token hashing is enabled by default in InfluxDB OSS 2.9.0
Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.
For more information, see Token hashing.
Security, access control, and sensitive secret handling are incredibly important when handling any sort of sensitive data. This section provides information about managing the security of your InfluxDB instance.
InfluxDB 2.x/1.x compatibility
If you upgraded from 1.x to 2.9,
use the influx v1 auth commands
to manage authorizations for the 1.x compatibility API.
Enable TLS encryption
Enable Transport Layer Security (TLS) and use the HTTPS protocol to secure communication between clients and InfluxDB.
Enable security features
Enable a collection of additional security and hardening features in InfluxDB OSS to better secure your InfluxDB instance.
Disable development features
Disable development features that may not be desirable in production.
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB OSS v2 and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.