Registry settings
There are several settings related to Enterprise Server that you can change in Microsoft Windows’ Registry. These settings control some overall settings that are very important for Enterprise Server. They are all of the type REG_SZ.
The registry settings are found in the Registry path HKEY_LOCAL_MACHINE\SOFTWARE\Omada\Omada Enterprise\{OmadaIdentity-Version}.
For information about making changes to the Windows Registry, see the Microsoft Support article.
Registry settings for Omada Identity
| Value name | Description |
|---|---|
DownloadLimit | Specifies the timeout in seconds for queries to the Enterprise Service database. |
PswEncryptionKey | Specifies the encryption key used to encrypt and decrypt strings. It is important that the key is the same as you use for Omada Provisioning Service. |
ConnStr | Specifies the connection string to the database. If you host several environments on the same machine, this should point to the master database. |
SolutionName | Specifies the value of the solution name from the registry key for SolutionName. |
Salt | Password salt for the symmetric encryption algorithm. |
CommandTimeout | Specifies the value for the registry key for CommandTime. This setting is the timeout settings for certain SQL commands. |
LoadBalancerNodeEnabled | Specifies the response returned by the Loadbalancer page. |
SessionTimeout | Specifies the value for the registry key for SessionTimeout. This setting is the authentication timeout settings for Forms and SAML/OpenID logon. |
PswEncryptionKey, ConnStr, SolutionName, CommandTimeout, LoadBalancerNodeEnabled, and SessionTimeout settings can also be set via the Web.config file.
Please note that, at the exception PswEncryptionKey, values of these settings set in the Web.config file take precedence over the registry values. In the case of PswEncryptionKey, the registry file value takes precedence. You can find more information in the Web.config configuration settings section.
Changing PswEncryptionKey after it has been used to encrypt data should be performed with caution as an incorrect update may lose data or Omada Identity unresponsive.