Introduction

URAC micro-service V3 configuration variables that are needed and can be customized 

1. Password generation configuration

You can change the values of the below variables to customize iterations, seeding, and the algorithm used to hash passwords.

2. 3rd party login configuration

URAC allows third party login via one of the below methods:

1. Passport Login: Define application keys for passport integration. Currently supporting Azure, Github, Twitter, Facebook, and Google. Got to the link for more information and an example of the configuration.
2. OpenAM login: SSO (Single Sign-On).
3. LDAP (Lightweight Directory Access Protocol) login: Active directory login.

3. Mail Configuration

Mail configuration can be found under two configuration objects:

1. Under common fields in order to be used in other microservices not only in URAC. This includes the transport configuration for the mail provider.
2. Under URAC configuration in order to customize mail options to handle URAC requirements. This includes links and content of emails sent in each stage.

More information about Variables used, custom data fields used in "content", and examples of the configuration can be found under Mail Notification Configuration

Examples: 

"commonFields" : {
  "mail": { // to control the smtp configuration
      "from": 'me@localhost.com',
      "transport": {...}
  }
}

"urac" : {
  "links": {...}, // this object to control the links in the emails
  "mail": { // this object to control the content of the emails
    "join": {...}, // Join - mail content configuration
    "forgotPassword": {...}, // Forgot password mail - content configuration
    "addUser": {...}, // Add User - mail content configuration
    "changeUserStatus": {...}, // Change User Status - mail content configuration
    "changeEmail": {...} // Change Email - mail content configuration
  }	
}

4. Pin login configuration

Pin code adds a second layer of authentication to URAC. For example, having restaurants with multiple branches and multiple positions. User should put a password and should use a pin code to gain access. For full information go to Pin Configuration.

5. Data 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 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.