Kiosks allow employees to use a shared device to submit punches and interact with activity forms through a web browser.
To configure Kiosks for use in the system, create the building blocks for Kiosks in Common Setup:
- Kiosk Instances - The Kiosk Instances page is used to define the characteristics of individual kiosk instances that can be started from a device.
- Kiosk Configurations - The Kiosk Configurations page is used to define how users can interact with a kiosk instance.
Kiosks can be used by start-stop employees, duration employees, attestation employees, and can optionally be configured for use by federated employees.
- Federated instances must be assigned to locations that use the federation authentication type.
- Non-federated instances must be assigned to locations that use the basic authentication type.
Uwaga: If a federated kiosk administrator accidentally starts a non-federated kiosk instance, the instance can be stopped using the Kiosk Instances configuration page. See Stop an active Kiosk Instance for more information.
Minimum requirements for IDP Configurations
Kiosks are designed to be used within a federated environment. By design, Kiosk operates in two authentication steps.
-
Managers with special privileges log into the Kiosk to start a kiosk instance. When logging into the application, a federated log-in page allows managers to provide their credentials. Once the manager is logged-in, they start an instance from the list of pre-configured kiosk instances. Once complete, the application logs the manager out to allow the Kiosk for general use.
-
A second authentication happens when an instance is started. Employees log-in into application using the same kiosk instance mentioned in the first step. Upon completion of each action (express punch, advance punch, punch with breaks, activity form submission) made by the employee, the application automatically logs the user out and prepares the instance for the next employee usage.
The minimum requirement for kiosks in a federated environment is that the SSO federated environment must return the control to the Kiosk after each logout. This applies between both authentication steps and between each usage of kiosk, within step two by different employees.For example:
If the Kiosk URL is < https://some-company-name.npr.mykronos.com/wfd/kiosk >, then the same URL should be returned by SSO server (IDP or SP initiated) after the manager starts an instance which essentially performs a log-out action.
Ostrzeżenie: This requirement is imperative for the Kiosk to function in a federated environment. If this re-direct to the original Kiosk URL is not performed, the application cannot be used as subsequent users will not have the chance to continue with their submissions.
When a federated environment is configured for general UKG Pro Workforce Management™, Kiosk specifics are taken into account. Kiosks use the same federated environment as UKG Pro Workforce Management™, but the implementation of UKG Pro Workforce Management™ and Kiosks id different. UKG Pro Workforce Management™ users log out by performing an explicit sign-out task, while Kiosk users, log out implicitly, in the background while performing a Kiosk related activity, like punch or form submission.