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.

More information can be found in the Complete Example

2. Join & Membership

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.

{
	"basic":{
		"groups": ["starter"]
	}
}

3. Mail Configuration

Mail configuration can be found under two configuration objects:

1. SMTP Configuration: 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. Email Content Configuration: 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 Configuration

Examples: In provision

"commonFields" : {
  "mail": { // to control the smtp configuration
      "from": 'me@localhost.com',
      "transport": {...}
  },
  "sms":{
	  "from": '16170000000',
      "twilio": {
         "accountSid": "WWWW",
         "authToken": "WWWW"
	  }
  }
},
"urac" : {
  "link": {...}, // 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
  },
  "sms": {
	"inviteToJoin": {...}
  }	
}

Examples: In custom registry

You should create to entries under custom registry (one for mail, one for urac, and one for sms) as follow:

with the following configuration content:

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

{
  "link": { // this object to control the links in the emails
		"addUser": "...",
		"changeEmail": "...",
		"forgotPassword": "...",
		"inviteToJoin": "...",
		"join": "..."
	},
  "mail": { // this object to control the content of the emails
    "addUser": {...}, 
    "changeEmail": {...}, 
    "changePin": {...}, 
    "changeUserStatus": {...}, 
    "forgotPassword": {...}, 
    "invitePin": {...}, 
    "join": {...},
    "resetPin": {...}
	"inviteToJoin": {...}
  },
  "sms": {
	"inviteToJoin": {...}
  }		
}

{ // to control the smtp configuration
      "from": '16170000000',
      "twilio": {...}
}

4. Mail token configuration

The URAC sends verification mail with links containing token with expiration date.

5. Pin login configuration

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.

6. Data configuration

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 can change the values of the below variable to turn on roaming among main tenants. Either you set masterCode or your set dbCodes.

{
	"0000_TENANTID_TO_000": {
		"0000_TENANTID_FROM_000": {
			"groups": ["optional", "..."]
		}
	}
}

{
	"TTTT": ["tCODE1", "tCODE2"]
	"XXXX": ["tCODE4", "tCODE5"]
}