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.

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

1. Under common fields in order to be used in other microservices not only in URAC.
2. Under URAC configuration in order to customize mail options to handle URAC requirements.

Examples:

"mail": {
        "from": 'me@localhost.com',
    "transport": {
    "type": "sendmail",
    "options": {}
  }
}

"mail": { //urac mail options
  "join": {
    "subject": 'Welcome to SOAJS',
    "path": "./mail/urac/join.tmpl"
  },
  "forgotPassword": {
    "subject": 'Reset Your Password at SOAJS',
    "path": "./mail/urac/forgotPassword.tmpl"
  },
  "addUser": {
    "subject": 'Account Created at SOAJS',
    "path": "./mail/urac/addUser.tmpl"
  },
  "changeUserStatus": {
    "subject": "Account Status changed at SOAJS",
    //use custom HTML
    "content": "<p>Dear <b>{{ username }}</b>, <br />Your account status has changed to <b>{{ status }}</b> by the administrator on {{ ts|date('F jS, Y') }}.<br /><br /> Regards,<br/> SOAJS Team. </p>"
  },
  "changeEmail": {
    "subject": "Change Account Email at SOAJS",
    "path": "./mail/urac/changeEmail.tmpl"
  }
}

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

1. Default Configuration

Default Configuration layer That can be overridden by one of the below configuration layers.

2. Registry Configuration 

Table and links to examples 

Database needed by URAC

3. Tenant Configuration

Table and links to examples 

Link to Complete example 

Configuration priority and the default values

This table illustrates the configuration that can be overridden at a different layer of configuration 

model¹: We currently only support mongo models.