The settings for the backend of the server are stored in the appsettings.json located in the root directory of the Raynet One Data Hub installation (by default C:\Program Files (x86)\Raynet One Data Hub directory).
Available settings:
•InternalDatabase – connection string to Raynet One Data Hub private database.
•Connection strings – the list of "DataSources" available for creating reports and dashboards. By default only one string will be available there – the connection string to "Result" database.
•Secret (within the TokenManagement section) – a unique secret key used for JWT token generation and validation. This value must be unique for each Data Hub installation and must be kept secure.
•InitialTenant – specifies the tenant that users are assigned to when logging in via external identity management (e.g., KeyCloak) if they have no tenant assignments. This setting is part of the ExternalIdentityManagement configuration. The default value is Default.
•Security – controls HTTP security response headers. This section allows administrators to configure Content Security Policy (CSP), trusted network and proxy definitions, allowed origins for cross-origin requests, and frame embedding behavior. See Security Header Configuration for details.
Token Management Secret
The Secret setting is located in the TokenManagement section of appsettings.json. It defines the secret key used to sign and validate JSON Web Tokens (JWT) for authentication and shared link generation.
This value must be unique for each Data Hub installation. Use a strong, randomly generated string. Never reuse the same secret across multiple installations or share it publicly.
|
Warning: Changing the Secret value after the initial installation will invalidate all existing shared links for reports and dashboards. Users who access those links will receive an error. If you need to change this value, inform all users beforehand and regenerate shared links as needed after the change. |
Initial Tenant Configuration for External Identity Management
The InitialTenant setting is part of the ExternalIdentityManagement configuration and is used exclusively when external identity providers such as KeyCloak are configured. This setting determines which existing tenant a user should be automatically assigned to during login if they have no tenant assignments. The tenant must already exist in the system.
Configuration Details:
Property |
Description |
|---|---|
Setting Name |
InitialTenant |
Configuration Section |
ExternalIdentityManagement |
Default Value |
Default |
Data Type |
String |
When This Setting Applies:
•Only when external identity management (e.g., KeyCloak) is enabled and configured
•During user login via the external identity provider
•When the authenticated user has no tenant assignments in Raynet One Data Hub
Example Use Case:
A user authenticates via KeyCloak and successfully logs into Raynet One Data Hub. If this user has not yet been assigned to any tenant in the system, they will be automatically assigned to the tenant specified in the InitialTenant setting (by default "Default"). This allows users to access the application immediately without requiring manual tenant assignment by an administrator.
|
Important: This setting does NOT create a new tenant and has no effect on tenant creation during initial installation. The tenant name specified by InitialTenant must already exist in the system. This setting only applies when using external identity providers (such as KeyCloak) and only controls the automatic tenant assignment for users who have no tenant assignments when they log in. |
