Chrome OS Version: 52.0.2743.85
Chrome OS Platform: 8350.60.0
Prerequisite:
The forced installed Certificate Enrollment for Chrome OS extension requires a config JSON file to be applied via CPanel.
Extension: fhndealchbngfhdoncgcokameljahhog
Extension policy: https://support.google.com/chrome/a/answer/6321820?hl=en
Managed profile for EAP-TLS wifi network.
Issue:
The "enable_auto_enrollment" value in the policy is ineffective, True or False do not behave differently:
"enable_auto_enrollment": {
"Value": false
}
The extension policy documentation states:
enable_auto_enrollment — Control whether the extension initiates enrollment automatically or waits for the user attempt at connecting to the EAP-TLS network. Default is false.
This suggests True would automatically prompt the user once the policy has come down to enroll to get a certificate, this doesn't occur.
Steps To Reproduce:
(1) Setup the Certificate Enrollment extension to be forced installed.
(2) Create a managed EAP-TLS wifi profile (Client Enrollment URL: chrome-extension://fhndealchbngfhdoncgcokameljahhog/html/request_certificate.html )
(3) Have the policy JSON "enable_auto_enrollment" set to True.
Expected Result:
The user should be prompted or immediately directed to chrome-extension://fhndealchbngfhdoncgcokameljahhog/html/request_certificate.html once the Certificate Enrollment extension policy has come down.
It should not wait for the user to select the EAP-TLS AP that requires certificate before the extension is initiated for enrollment.
Actual Result:
The extension is not automatically initiated to prompt the user to enroll for a certificate.
User still needs to select the EAP-TLS AP, as though this value was set to False.
Customer would like to have the users prompted immediately upon first sign-in to enroll for a certificate, so that it can automatically switch to the EAP-TLS network without user action.
|
Deleted:
Certs_Policies_1.pdf
119 KB
|
|
Deleted:
debug-logs_20160729-105027.tgz
72.1 KB
|
|
debug-logs_20160729-105027.tgz
72.1 KB
Download
|
Comment 1 by gbirtchnell@chromium.org
, Aug 16 2016