Step 3 - Using the Service Manager
After making configuration changes within the HMAC Service the service must be restarted for the changes to take effect. The HMAC service manager module allows operators to start, stop or restart the HMAC service as well as make changes to service related configurations. Click on the "Service Manager" button and this screen will be shown:
The configuration items are as follows:
| Item | Description |
| Service Address | The address of the HMAC Service is being controlled from this Service Manager. Ensure the address points to the correct service URL, i.e. if you are running the service on multiple machines in a load-balanced configuration then check that the name is correct for the particular instance that needs to be started/stopped/restarted. By default it will be that of the local machine. |
| Start | Start the service. Status will change to “Running” after a successful start. |
| Stop | Stop the service. Status will change to “Stopped” after the service is stopped. |
| Restart |
Stop and then start the service in one go, Status will change to “Running” after a successful restart. |
| Log HMAC Transactions | When the Log HMAC transactions option is enabled then all HMAC transactions are recorded in the ADSS Server database. When this option is disabled, no HMAC transactions will be recorded in the database. This feature is useful when much higher throughput is required and logging is seen as an overhead. |
| HMAC key to Generate OAuth Tokens | Select HMAC key which is already configured in the Key Manager. The HMAC Key will be used by ADSS HMAC Service to generate the OAuth tokens. A default HMAC key comes pre-bundled with the ADSS Server installation. This can be replaced with operator generated HMAC keys that may either exist in software (database) or on a PKCS#11 device e.g. an HSM. |
Ensure any changes are saved by clicking the Save button and restart the service to take changes effect.