Issue metadata
Sign in to add a comment
|
[Enterprise] [policy pushed] Selecting EAP-TLS networks does not prompt user to "Get new certificate" |
||||||||||||||||||||
Issue descriptionChrome Version: <From about:version: Google Chrome 71.0.3578.73 > Chrome OS Version: <From about:version: Platform 11151.47.0> Chrome OS Platform: <Nocturne> Network info: <WiFi Enterprise policy> Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1) Connect to configured EAP-TLS network. (2) The policy should have client enrollment URL. (3) Click to connect to EAP-TLS network. Expected Result: Pop-up to get new certificate. Actual Result: No pop-up. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always. What is the impact to the user, and is there a workaround? If so, what is it? user needs to manually go the url to download certificate required for connection. Please provide any additional information below. Attach a screen shot or log if possible. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report. Will update if it is reproducible on stable/dev builds. +Enterprise test team who checked on other DUTs.
,
Dec 3
Assigning to marcuskoehler for CrOS triage.
,
Jan 8
Is this still reproducible? Sounds like something we should fix.
,
Jan 8
,
Jan 8
Hi Pavol, we have the following behavior here: 1. When clicking to connect to EAP-TLS network from the tray, it shows the pop-up and then redirects to configured URL (Screenshot 1). 2. When clicking to connect to EAP-TLS network from the settings, it doesn't show the pop-up (Screenshot 2) and looks like there is no way to install the certificate. Could you please confirm if this is WAI? Thanks!
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by aashuto...@chromium.org
, Nov 30