forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Change-Id: I6f552db37fe1d1d7207dba715e7c613377bd67eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1588400 Commit-Queue: Jacob Dufault <jdufault@chromium.org> Reviewed-by: Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#655069}
- Loading branch information
1 parent
acacc90
commit 4260b14
Showing
3 changed files
with
38 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# Enterprise Enrollment on Login | ||
|
||
The easiest way to test enterprise enrollment on login is to use an actual | ||
enterprise account. If you don't have one, reach out a teammate; anyone with an | ||
account can add new accounts. | ||
|
||
Once you have an enterprise account, run chrome and [enroll the device](https://support.google.com/chrome/a/answer/1360534?hl=en). The shortcut combo is | ||
`Ctrl+Alt+E`. | ||
|
||
If you're testing on device and wish to clear enrollment state, the easiest way | ||
is to run `crossystem clear_tpm_owner_request=1` and then reboot. This clears | ||
TPM state which will destroy cryptohome and enrollment state. When the device | ||
boots next it will check and see if it needs to be force re-enrolled. | ||
|
||
Policy can be configured at admin.google.com; log in with your enterprise | ||
account. Whoever created the account should have granted you superuser | ||
privileges. You may need to log in using an incognito window if your primary | ||
Google account is part of an enterprise domain. | ||
|
||
When you're changing policies in admin.google.com, pay attention to the | ||
organization you are modifying. Try to only adjust your test organization to | ||
avoid propagating changes to other users. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
# Debugging UI | ||
|
||
The login and lock screen can run with a developer overlay that make common | ||
operations such as setting up a device with 10+ users trivial. Pass the flag | ||
`--show-login-dev-overlay` when running chrome and the UI will automatically | ||
appear. | ||
|
||
```sh | ||
./out/Release/chrome --show-login-dev-overlay | ||
``` | ||
|
||
The overlay will use fake data where necessary to show the relevant UI; buttons | ||
are mostly functional but may break since fake data may be sent to chrome. |