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 | 12 |
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
...
| Info | ||
|---|---|---|
| ||
In provision - key configuration In custom registry - urac |
You can change the values of the below variables to customize if you want the user to validate their email once they join or not.
| Name | Type | Description | Example | ||
|---|---|---|---|---|---|
| validateJoin | Boolean | This configuration controllers the status of a user after joining. aka ('pendingJoin' : 'active') | true | ||
| membership | Object | This configuration allows you to configure different type of membership that can be set while joining to drive different user configuration like group (make sure the group is available) we only support an array of 1 group for now. |
|
...
| Info | ||
|---|---|---|
| ||
In provision - key configuration In custom registryregistry - mail & urac |
Mail configuration can be found under two configuration objects:
...
| Info | ||
|---|---|---|
| ||
In provision - key configuration In custom registry - urac |
The URAC sends verification mail with links containing token with expiration date.
...
| Info | ||
|---|---|---|
| ||
In provision - key configuration In custom registryregistry |
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.
...