Introduction
...
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 | dbCodes | ObjectTo consolidate the main tenant users and create roaming capabilities among them by invitation only |
Info |
---|
{ "TTTT": ["tCODE1", "tCODE2"] "XXXX": ["tCODE4", "tCODE5"] } |
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 | ||
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. |
|
...
You should add a database configuration to the environment where you deployed URAC. for more information go to Data Configuration.
7. Roaming among main tenants
You need to add the following into custom registry
Info | ||
---|---|---|
| ||
In custom registry - urac |
You can change the values of the below variables to customize iterations, seeding, and the algorithm used to hash passwords.
Name | Type | Description | Example | ||
---|---|---|---|---|---|
dbCodes | Object | To consolidate the main tenant users and create roaming capabilities among them by invitation only |
|