Intel AMT Features > User Consent > Use Cases > Full Consent Flow
CollapseAll image

Full Consent Flow

The following steps describe how to complete the full user consent process.

 Note:

To check the target system power state, examine the instance property CIM_AssociatedPowerManagementService.PowerState.

 

1.  Check the user consent (optIn) state, as described in Get User Consent Status.

2.  . If OptInRequired property is other than NONE, consent is required for some operations. If the OptInState property is “NOT STARTED” the flow can be continued. If it is a different state, do not attempt to restart the flow: if you do, the current flow will be terminated. If you want to start the flow from the beginning, you can reset the OptInState using the CancelOptIn method as described in Stop the Consent Process. If the OptInState is “RECEIVED” or “IN SESSION”, then the opt-in flow has completed – you can successfully start a redirection session. The following table summarizes this step:

OptInState Value

Action

NOT STARTED

Continue with the flow.

REQUESTED or DISPLAYED

Do not attempt to restart the flow. If you do, the current flow will be terminated. To restart, first invoke the CancelOptIn method.

RECEIVED or IN SESSION

Flow is complete. A redirection session can be started.

 

3.  Start the user consent process, as described in Start the Consent Flow. A consent code should be generated by Intel AMT, and displayed at the target host monitor.

4.  Query the OptInState property to see if it has changed. If it has changed, proceed to step 5. Note: It may take up to 15 seconds for the OptInState to propagate to the correct value. If the state has not changed after 15 seconds, proceed to step 5.

5.  Examine the OptInState property:

a.   If the value is DISPLAYED: Sprites are supported. If the user cannot see the Sprite go to step 7 to switch monitors. Otherwise go to step 8.

b.   If the value is REQUESTED: The Sprite was not displayed because Sprites were disabled by the OEM. The code will be displayed via the BIOS - a reboot must be done locally or remotely. Go to step 6.

6.  Reboot the system: You may use the CIM_PowerManagementService.RequestPowerStateChange method to boot the system or request the user to perform a reboot. If the user consent code is not displayed, either by the MEBx or via a Sprite, go to step 7. Otherwise, continue with step 8.

7.  Switch display monitors: If the display monitor should be switched (the user does not see the consent Sprite), see Set the Default Monitor Property.

8.  Check the OptInState (because of the slowdown mechanism; see Denial-of-Service Attack Prevention). If the OptIn state is “NOT STARTED”, return to step 1. Otherwise, continue.

9.  Send the user consent code, obtained from the user, as described in Send Consent Code.

10. Perform the task that requires user consent.

11. On completion of the task, cancel the current opt-in session by invoking the Stop the Consent Process flow.

Instance Diagram

Classes Used in This Flow

SDK Sample

If there is a sample demonstrating this flow, it is included in the SDK installation file. See SDK Installation Layout for details.

 

See Also:

   KVM user consent flow

   User Consent Tool

 

Copyright © 2006-2022, Intel Corporation. All rights reserved.