Tommy, do you have cycles to work on this, or should I polish it up?

michaelpg@ - Is there a way to simulate signing in to a public session in a linux chromeos build?

+xiyuan@ - Do you know if it is possible to simulate a public session in a linux chromeos build, or can you point me to how to set up a device to be in public session mode?

I don't think there is a way to setup pubilc session via command line. The public session account is only created from policy and our dev box does not read the policy blob from outside.

I was using YAPS. Check out this doc about how to setup your personal DM server (and a poor-man's protoc buffer editor):
https://docs.google.com/a/google.com/document/d/1HiSuCNESc6tOQxx2QdmYATy4mT_e1zUaocmqUvJyWeU/edit?usp=sharing

After that, the public session account is set up as part of a DeviceLocalAccount, find that in device policy and add it there.

Then enroll your device to the test DM server, and you will get it on the login screen.

Ugh, that's a lot of things I've never done.

Michael, can I task you with addressing this?

Also, should we handle public sessions like guest sessions and just hide the People section?

+tbuckley@

I used to be able to run a policy server locally, but thanks to issue 275291 the --disable-policy-key-verification flag no longer works. We have built-in flags for domains like managedchrome.com which I don't have an account for, and trying to use a Gmail account fails with "Policy is missing public_key_verification_signature".

I'll keep trying...

answer to #10 was: get a @managedchrome.com account. see my comment on the internal Test DMS User Guide doc for more.

We'll just hide People in public account sessions.

Other problems with public account sessions are tracked in  issue 682107 .

This has been done and other issues audited ( issue 688471 ).