Skip to Content
Product GuideKeep the secrets

Keep the secrets

Setup generates five secrets once, writes them to .novuslens.env and keeps them on a later setup. The file also holds the initial operator’s sign-in. Keep it private and never commit it.

SecretProtectsIf changed
Database passwordthe databasedo not change it: the database keeps the password it was created with
Session secretthe login cookieCookieA small value a browser keeps and sends back to a website. NovusLens uses a signed cookie to remember the signed-in account.everyone is signed out
Identity saltIdentity saltA secret value added before employee identifiers are turned into fingerprints. Keep the same value so later imports can still match existing people.the sealed personnel hashesHashA fixed-length fingerprint calculated from content. Comparing fingerprints helps detect changes and match records.never change it: every sealed person mapping is orphaned
Service tokenService tokenA secret value sent with requests between NovusLens services. The receiving service refuses requests with a missing or wrong value.the hop from the web application to the reasoning service./lens start restarts both
GatewayGatewayA service that accepts requests and passes them into another system. The Mycelium gateway gives NovusLens access to the mesh. tokenthe meshMeshA set of connected Mycelium services that exchange updates and keep the NovusLens log. gatewaydata on disk is unaffected

Every service runs in the customer profileDeployment profileA setting that selects customer or development behaviour. Customer mode refuses development credentials and uses the signed-in session as the identity. and refuses a missing, public or short secret. To change one that may have been exposed, follow Secrets.

Copy .novuslens.env into the customer’s approved secrets store before importing personnel records. A backup archive holds the file too, so keep each archive as private as the file. Restored personnel links need the original identity salt.

Read more

Last updated