Introduction
URAC micro-service V3 configuration variables that are needed and can be customized
...
1. Password generation variables
You can change the values of the below variables to customize iterations, seeding, and the algorithm used to hash passwords.
...
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 | "aes-128-cbc-hmac-sha256" or "des". You can go to List of Crypto Algorithms to find the name of the algorithm that you can use. |
2. Passport Login variables
Define application keys for passport integration. Currently supporting Twitter, Facebook, and Google. For more information and an example of the configuration, go to Passport Login.
3. Mail Configuration variables
- Under common fields in order to be used in other microservices not only in URAC.
- Under URAC configuration in order to customize mail options to handle URAC requirements.
...
Variables used, custom data fields used in "content", more information, and examples of the configuration can be found under Mail Notification Configuration
4. Pin configuration variables
Pin configuration is made to add a second layer of authentication to URAC. For full information go to Pin Configuration
5. Registry configuration
Resources and database creation steps can be found under Database needed by URAC. More information can be found under the registry configuration layer below.
Configuration Layers and Levels
...
Name | Local Configuration (Default) config.js | Registry Configuration (Per Environment) req.soajs.registry | Tenant Configuration (Per Tenant Per Environment) | |
---|---|---|---|---|
Settings | Custom | |||
pinConfiguration | ✓ | ✓ | ✓ | |
model¹ | ✓ | ✓ | ||
hashIterations | ✓ | ✓ | ||
seedLength | ✓ | ✓ |
model¹: We currently only support mongo models.
...