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

Issue 693560 link

Starred by 1 user
Status: Started
Owner:
antrim@chromium.org
Cc:
atwilson@chromium.org
emaxx@chromium.org
pmarko@chromium.org
█ krishna...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Add support for affilitaion IDs to YAPS

Project Member Reported by pmarko@chromium.org, Feb 17 2017 
YAPS (the test enterprise policy server) does currently not provide affiliation IDs. To test with an affiliated user, there is the --user-always-affiliated flag on the client, evaluated in https://cs.chromium.org/chromium/src/chrome/browser/chromeos/login/users/affiliation.cc?type=cs&q=IsUserAffiliated&l=31 .

It will make testing easier and less surprising when affiliation works out of the box with YAPS.

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

Cc: trapti@chromium.org jingwee@chromium.org krishna...@chromium.org

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

For reference: CL which added the flag: https://codereview.chromium.org/2545523003

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

Cc: pmarko@chromium.org
 Issue 725339  has been merged into this issue.

Comment 4 by pmarko@chromium.org, Aug 16 2017

Owner: antrim@chromium.org
Assigning to Dennis after offline discussion as he's working on new YAPS features and this might be easy to do on that occassion.

Comment 5 by antrim@chromium.org, Aug 16 2017

Status: Started (was: Assigned)

Comment 6 by jingwee@chromium.org, Jun 23 2018

Cc: -trapti@chromium.org -jingwee@chromium.org
►

Sign in to add a comment