Changed Windows account to run service.

Removed default account for service.
Added required options run-as-user and run-as-password.
Added code to set security rights required to run service.
File access and chrome binary checks changed from fatal error to just error message.

BUG=141243
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=151652

[Vitaly Buka (NO REVIEWS), 2012-08-14 19:32:01]

Please review.

[Albert Bodenhamer, 2012-08-14 20:38:18]

https://chromiumcodereview.appspot.com/10824294/diff/7001/cloud_print/service...
File cloud_print/service/win/cloud_print_service.cc (right):

https://chromiumcodereview.appspot.com/10824294/diff/7001/cloud_print/service...
cloud_print/service/win/cloud_print_service.cc:29: const wchar_t
kUserToRunService[] = L"NT AUTHORITY\\SYSTEM";
I'm a bit nervous running as SYSTEM by default.  Any chance we could pull
credentials for the current user and use that as the default?

https://chromiumcodereview.appspot.com/10824294/diff/7001/cloud_print/service...
File cloud_print/service/win/local_security_policy.cc (right):

https://chromiumcodereview.appspot.com/10824294/diff/7001/cloud_print/service...
cloud_print/service/win/local_security_policy.cc:23: class ScopedLsaFreeMemory {
The transition of ownership here bothers me, though I'm not sure of a better
way.

Should we consider adding this somewhere more central?

[Vitaly Buka (NO REVIEWS), 2012-08-14 20:58:51]

https://chromiumcodereview.appspot.com/10824294/diff/7001/cloud_print/service...
File cloud_print/service/win/cloud_print_service.cc (right):

https://chromiumcodereview.appspot.com/10824294/diff/7001/cloud_print/service...
cloud_print/service/win/cloud_print_service.cc:29: const wchar_t
kUserToRunService[] = L"NT AUTHORITY\\SYSTEM";
For current user we need to ask password.
Probably for default is better to have something without one.
I can rollback to LocalService but some users reported that they can print with
SYSTEM but not LocalService 
On 2012/08/14 20:38:18, Albert Bodenhamer wrote:
> I'm a bit nervous running as SYSTEM by default.  Any chance we could pull
> credentials for the current user and use that as the default?

https://chromiumcodereview.appspot.com/10824294/diff/7001/cloud_print/service...
File cloud_print/service/win/local_security_policy.cc (right):

https://chromiumcodereview.appspot.com/10824294/diff/7001/cloud_print/service...
cloud_print/service/win/local_security_policy.cc:23: class ScopedLsaFreeMemory {
I am not sure what do you mean.

On 2012/08/14 20:38:18, Albert Bodenhamer wrote:
> The transition of ownership here bothers me, though I'm not sure of a better
> way.
> 
> Should we consider adding this somewhere more central?

[Vitaly Buka (NO REVIEWS), 2012-08-14 21:51:00]

https://chromiumcodereview.appspot.com/10824294/diff/7001/cloud_print/service...
File cloud_print/service/win/cloud_print_service.cc (right):

https://chromiumcodereview.appspot.com/10824294/diff/7001/cloud_print/service...
cloud_print/service/win/cloud_print_service.cc:29: const wchar_t
kUserToRunService[] = L"NT AUTHORITY\\SYSTEM";
Removed default user.

On 2012/08/14 20:58:51, Vitaly Buka wrote:
> For current user we need to ask password.
> Probably for default is better to have something without one.
> I can rollback to LocalService but some users reported that they can print
with
> SYSTEM but not LocalService 
> On 2012/08/14 20:38:18, Albert Bodenhamer wrote:
> > I'm a bit nervous running as SYSTEM by default.  Any chance we could pull
> > credentials for the current user and use that as the default?
>

[Albert Bodenhamer, 2012-08-14 22:32:29]

lgtm

[commit-bot: I haz the power, 2012-08-14 22:55:41]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/vitalybuka@chromium.org/10824294/10009

[commit-bot: I haz the power, 2012-08-15 00:31:00]

Try job failure for 10824294-10009 (retry) on win_rel for step "runhooks".
It's a second try, previously, step "interactive_ui_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[commit-bot: I haz the power, 2012-08-15 00:31:57]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/vitalybuka@chromium.org/10824294/10009

[commit-bot: I haz the power, 2012-08-15 02:10:32]

Try job failure for 10824294-10009 (retry) on linux_rel for step
"interactive_ui_tests".
It's a second try, previously, step "interactive_ui_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_rel&...

[commit-bot: I haz the power, 2012-08-15 02:11:52]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/vitalybuka@chromium.org/10824294/10009

[commit-bot: I haz the power, 2012-08-15 04:25:55]

Change committed as 151652