Configuring the Unity Service

The order in which the steps are done is not important; it is possible to go back to an earlier step and make changes later if required.

Steps	Description
Step 1:	Configure one or more Unity Profiles that will be relevant for managing users, signing keys, authorised devices, authorisation requests, signing requests, getting the signed hash (i.e. PKCS#1 signature) and their current statuses. Client applications refer to the Unity Profile within their request messages sent to the ADSS Unity Service.
Step 2:	Register one or more client applications within the Client Manager. These can now be authorised to make requests to one or more Unity Profiles.
Step 3:	Configure the Email & SMS Settings which will be used to send the OTPs to the user's registered email address and mobile number for user device registration.
Step 4:	Use the ADSS Unity Service Manager to start/stop/restart the service. ADSS Unity Service is required to be restarted when either there is a change in Unity service manager configurations or a Unity Profile is added/updated/deleted.

Each of these is described in the sections that follow: