This scenario is an example of use of the hybrid flow manager.
In Linqui’s scenario, she uses the Cloud4all/GPII system with a kiosk that is running in its hybrid/untrusted device mode. In this mode, the application flow is split across a local and cloud-based set of components. This is done to ensure that the user’s complete NP set never reaches the device (since it is untrusted). Instead, only filtered, transformed settings that are scoped to the particular device are shared with the local infrastructure.
The flow can be seen in the sequence of the figure below. When Linqui logs in via the kiosk’s User Listener, a request is sent as usual to the local Flow Manager, which in turns fetches information about the device from the Device Reporter.
At this point, the flow diverges from the trusted device mode that Jim used above. Instead, the user token, Kiosk ID, and device information is sent to a cloud-based FM running in hybrid mode. Here, the solution information and user preferences are retrieved as normal. The first phase of the matchmaking process is carried out in the cloud, resulting in a set of system configuration instructions that contain only preferences and settings relevant for the kiosk. This information is then passed back to the local device, which carries out the second part of the matchmaking process, namely evaluating the current context and translating the preferences into settings that are understandable by the kiosk. These settings are finally passed back to the kiosk to be applied.