New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 851653 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Users get prompted for Pre-Shared Key (PSK) when connecting to L2TP VPN

Project Member Reported by ykrychala@google.com, Jun 11 2018

Issue description

ChromeOS version: 65/66.0.3359.203
ChromeOS device model: Chromebook 14 for work, others
Case#: 16054003

Description:
Customer has been experiencing an issue where their VPN on managed Chromebooks stopped working. Their users have been getting prompts to enter a pre-shared key when connecting to VPN

Steps to reproduce: 
- Add L2TP VPN in Admin Console
- Specify credentials (including PSK) in VPN profile
- Login to Chromebook
- Connect to VPN

Current Behavior / Reproduction: 
- User is prompted to enter PSK in VPN config window, PSK is NOT populated

Expected Behavior: 
- User got connected to VPN

Drive link to policies: 
https://drive.google.com/open?id=1LmptM_usginQQprbGaVtZaSi6wMsm0aL

Troubleshooting steps taken: 
- VPN works fine when manually configured with the same PSK. 
- Re-entered the PSK in the Admin console. 
- Created a new VPN profile in the Admin console and it propagated to Chromebooks but had the same issue with the PSK. 
- Auto Connect has been left disabled for business reasons. 
- Issue has been confirmed in Chrome OS M65 and M66. 
- Chromebooks able to connect to Wi-Fi no problem. 

I was able to reproduce the issue locally. PSK is present in VPN configuration according to policies. The issue has no relation to VPN functionality itself (it works fine), but seems to be an UI bug. However, since users do not know PSK, they cannot connect to VPN so this issue is serious for the customer.

Please let me know if more information/logs is needed.

 
Components: Internals>Network>VPN UI>Shell>Networking
Labels: -Pri-2 Pri-1
Cc: cernekee@chromium.org
Labels: M-68
Owner: steve...@chromium.org
Status: Assigned (was: Unconfirmed)
It is likely to late to fix this for 67, but we should be able to fix it for 68.

Can you inspect the network configuration in chrome://network with 'Property format' set to 'Shill'? What is the value of 'Connectable' (when the UI is prompting for a password)?


Status: Fixed (was: Assigned)
I was not able to reproduce this on ToT (69.0.3457.0) or Dev channel (68.0.3440.15).

We made some fixes to this UI flow in 67 and 68, please verify on a more recent build.

Sign in to add a comment