Automated RESTful API configuration

Automation is used to configure RESTful API connectivity to multiple clocks and is recommended for most deployments. Configuration is delivered differently for clocks that are already deployed than for clocks that are not yet accessible.

If a clock is already deployed, it is accessible and can receive configuration updates. If a clock is not yet accessible, it remains in a staging or provisioning state and can be configured prior to deployment.

The current automation process does not require manual configuration on the clock. Credential values are prepared outside the clock and sent to the clock through configuration updates:
  1. Download the .ionapi file and identify the WFM Clocks API endpoint.
  2. The credential values are processed and encrypted using the same mechanisms used for other secure clock configuration values.
  3. The encrypted configuration is transferred to the clock using vendor provisioning for clocks that are not yet accessible or configuration update process for clocks that are already deployed.
  4. The clock applies the updated configuration during its normal update.
Note: When updating the settings.conf file using the configuration update process, the update must include only the settings being added or modified. Each update must also include changes from previous updates.