Flow Chart and Diagram

These flow diagrams depict how the device agent for the Context-based MFA work in order to collect the device-related information.

Scenario1: If a customer is unable to fulfil cipher changes, follow the following flow chart and flow diagram created separately for Windows 10 and Windows 7/8/8.1 devices:

Flowchart

Flow Diagram-Windows 7/8

User with Windows 7/8 version on Laptop 

User with Windows 7/8 version in workstation   

Step 1: Users with Windows 7/8 version in Laptop or workstation with device agent access Cross Identity.

Steps 2 and 3: Cross Identity Router Controller communicates with the user using base URL and Cross Identity.

Step 4: Cross Identity invokes the On-prem Device agent on the Windows machine indirectly and requests for device information via domain name, hostname, X509 Certificate etc.

Step 5: The device shares request details to Cross Identity and Rule verification starts.

Step 6: On Successful verification, the User is redirected to the Cross Identity launchpad.

Flow Diagram- Windows 10

User with Windows 10 version in laptop and Workstation   

Step 1: Users with Windows 10 version in Laptop or workstation with device agent access Cross Identity.

Step 2: Cross Identity invokes the On-prem Device agent on the Windows machine indirectly and requests for device information via domain name, hostname, X509 Certificate etc.

Step 3: The device shares request details to Cross Identity and Rule verification starts.

Step 4: On Successful verification, the User is redirected to the Cross Identity launchpad.

Scenario 2: If the Customer can fulfil cipher changes then use the generic flow chart:

Flow Chart

Flow Diagram-Windows OS

User with any Windows OS on laptop and Workstation 

 

Step 1: Users with any Windows OS version on a Laptop or workstation with device agent access Cross Identity.

Step 2: Cross Identity invokes the On-prem Device agent on the Windows machine indirectly and requests for device information via domain name, hostname, X509 Certificate etc.

Step 3: The device shares request details to Cross Identity and Rule verification starts.

Step 4: On Successful verification, the User is redirected to the Cross Identity launchpad.