Introduction
URAC micro-service V3 configuration variables that are needed and can be customized
...
| Name | Type | Description | Example |
|---|---|---|---|
| hashIterations | integer | Hashing iteration value used by SOAJS hasher to encrypt/compare passwords | 16 |
| seedLength | integer | Seed length value used by SOAJS hasher to encrypt/compare passwords | 32 |
optionalAlgorithm | string | Password Hashing algorithm name. "aes256" or "des". You can go to List of Crypto Algorithms to find the name of the algorithm that you can use. You do not need to set this configuration if you do not want to specify an algorithm | aes256 |
More information can be found in the Complete Example
...
| Name | Type | Description | Example |
|---|---|---|---|
| validateJoin | boolean | This configuration controllers the status of a user after joining. aka ('pendingJoin' : 'active') | true |
3. Mail Configuration
...
Pin code adds a second layer of authentication to URAC. For example, in the hospitality business you want the manager to login and turn on pin login. This way a user can key in a ping and get access. For more information go to Pin login Configuration.
6. Data configuration
You should add a database configuration to the environment where you deployed URAC. for more information go to Data Configuration.
Configuration priority and the default values
This table illustrates the configuration that can be overridden at a different layer of configuration
| Info | ||
|---|---|---|
| ||
Local → Registry → Tenant
|
Name
Local Configuration (Default)
config.js
...
Registry Configuration (Per Environment)
req.soajs.registry
...
...
hashIterations
...
.