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

Issue 845424 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Enterprise kiosk apps not caching data

Reported by ad...@sjp.chrome-eval.com, May 22 2018

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10323.62.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.184 Safari/537.36
Platform: 10323.62.0 (Official Build) stable-channel sand

Steps to reproduce the problem:
1. Enroll device in chrome enterprise
2. Add Amazon Workspaces as a kiosk app and force software to load on bootup
3. Enter registration code (provided to all AWS users)

What is the expected behavior?
AWS registration code should be cached after being entered for the first time. This means when the device is next powered on the app will open initially and take a second or two to authenticate and initialise.

What went wrong?
Registration code details are not being cached (there is an option to cache this which is selected by default at the registration code screen). Will then hang for ages initialising software before allowing user to log in. When shut down, this will happen again and will require the reg code again.
This issue does not occur if the app is opened manually as it will cache the reg code initially and app will open instantly. Only seems to be a problem when app is forced open as a kiosk app in Chrome Enterprise.

Did this work before? Yes Unknown - never noticed this issue previously

Chrome version: 65.0.3325.184  Channel: stable
OS Version: 10323.62.0
Flash Version: 29.0.0.113 

Every now and then the issue will not occur and it seems to cache the details, then when trying again a few hours later it reverts back to not storing these details. Checked all settings in both browser and Chrome Enterprise and there is nothing set to remove or delete any cached data. Issue is worsened when network connectivity is slow.
 
Cc: pastarmovj@chromium.org
Components: -Services>Sync Enterprise
It doesn't look like sync related.

Adding enterprise to help in triage.
Cc: bartfab@chromium.org atwilson@chromium.org
Could you log in as a regular user on this device, navigate to chrome://policy and post its contents here, with all sections expanded?
Cc: dskaram@chromium.org
Components: UI>Shell>Kiosk
I'm not certain how the Amazon Workspaces app saves its data - have you reached out to the developer of that app for support first?
Cc: ljusten@chromium.org
Labels: Enterprise-Triaged Needs-Feedback
Status: (was: Unconfirmed)
Status: Unconfirmed
Owner: poromov@chromium.org
Status: Assigned (was: Unconfirmed)
I'm not clear this should be owned by us - best to drive this through chrome support since we don't really have a repro case here or any indication that this is anything other than a bug with Amazon Workspaces. Shall we WontFix this?
It could also be that ephemeral mode is set for the devices - we don't have any policy info that Bartosz requested in #3. 
However, not sure how ephemeral affects kiosk sessions.
Ephemeral mode causes kiosk sessions to become ephemeral as well, even though this is wrong (see bug 362593).
Owner: ----
Status: WontFix (was: Assigned)

Sign in to add a comment