Security Secrets (Reference)

Scripts → Tutorial | Concept | How-to Guide | Reference

Configuration Properties

Each Secret has the following properties:

PropertyDescriptionRequired

NameUnique identifier for the secretYes

SecretTypeDefines type of secret (e.g., Password)Yes

SecretValueEncrypted credential valueYes

DescriptionOptional notes or purposeNo

Only administrators can edit SecretValue. Standard users can reference existing secrets but not view them.

Example

Usage in Configuration

• In Datasets, select Secret instead of a raw password to bind connection strings.
• In Device/TagProviders (MQTT, OPC UA, etc.), reference secrets using /secret-<name>.
• Secrets allow safer credential management and support configuration portability.

Example: Assigning Secret1 to RuntimeUsers database login password.

Best Practices

1. Create secrets centrally in Security → Secrets.
2. Always prefer Secret over plain passwords in datasets and devices.
3. Restrict edit permissions — only admins should manage secret values.
4. Use descriptive names for clarity (e.g., DBRuntimePass instead of Secret1).
5. Document secret usage in the Description field for auditability.

In this section...