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

Issue 725339 link

Starred by 1 user
Status: Duplicate
Merged: issue 693560
Owner:
pmarko@chromium.org
Closed: May 2017
Cc:
█ trapti@chromium.org
█ jingwee@chromium.org
pmarko@chromium.org
█ krishna...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 721495


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

chrome.enterprise.platformKeys.getTokens API fails when connecting to YAPS

Project Member Reported by jingwee@chromium.org, May 23 2017 
Chrome Version: 60.0.3105.0
OS: ChromeOS 9574.0.0

What steps will reproduce the problem?

(1) On YAPS, configure ExtensionInstallForcelist with "hoppbgdeajkagempifacalpdapphfoai;https://clients2.google.com/service/update2/crx" for the PlatformKeys Test Extension.
(2) Enroll device to YAPS.
(3) Sign in, wait for a few minutes for the extensions to be installed. Sign out and sign in again. (Due to a separate issue, during the first session after enrollment, the API call stucks at "Getting the user and system token ...")
(4) Launch the extension chrome-extension://hoppbgdeajkagempifacalpdapphfoai/main.html
(5) Check the "Get user token" status which is the first text field on the page.

What is the expected result?
"OK: Found tokens: user, system."

What happens instead?
"Found tokens: user. Did not find tokens: system"

This issue seems similar to #722677 but does not reproduce when connecting to production DM server.
debug-logs_20170522-184112.tgz
106 KB Download
Screenshot 2017-05-22 at 6.40.40 PM.png
68.0 KB View Download
Screenshot 2017-05-22 at 6.41.02 PM.png
128 KB View Download

Comment 1 by pmarko@chromium.org, May 23 2017

Owner: jingwee@chromium.org
Oh, I forgot to warn you about this, sorry!
I think what you're seeing is a consequence of bug 693560 (CCed you to it):
YAPS currently does not support "affiliation IDs". This means that when signing in to YAPS, all users (regardless of domain) are treated as not affiliated by default.
The "--user-always-affiliated" command-line flag has been added in Dec 2016 to provide a way to test affiliated users with YAPS.[1]

What this means:
When chrome is connected to YAPS and ...
- chrome_dev.conf contains the --user-always-affiliated flag, all users are treated as affiliated (regardless of domain)
- chrome_dev.conf does not contain the --user-always-affiliated flag, all users are treated as not affiliated (regardless of domain)

As access to the system token through the extension API is only allowed for affiliated users, the flag must be in the file for the system token to be shown here.

Please confirm if adding the flag resolves this issue so I can either mark this as a duplicate of the mentioned bug 693560 or start a separate investigation.
Thanks!

[1] CL adding the flag (no crbug): https://codereview.chromium.org/2545523003

Comment 2 by pmarko@chromium.org, May 23 2017

Cc: pmarko@chromium.org

Comment 3 by jingwee@chromium.org, May 23 2017 

Thanks pmarko@ adding the flag does resolve this issue.

Comment 4 by pmarko@chromium.org, May 24 2017

Cc: jingwee@chromium.org
Mergedinto: 693560
Owner: pmarko@chromium.org
Status: Duplicate (was: Assigned)
Thanks for confirming, jingwee@. I'm merging this issue into bug 693560.
►

Sign in to add a comment