google_api_key

[churnd]

Pardon if this is a dumb question, but I'm following the instructions here:  https://code.google.com/p/chromium/wiki/ChromotingBuildInstructions

I'm confused as to what my google_api_key should be.  When I go to my developers console, I try to create a new public API key but it asks if I want to create a Server, Browser, Android, or iOS key & I'm not sure which to do.

To be clear, I'm trying to build a .deb pkg for my Ubuntu systems so I can install the linux host service.  I'm trying to build this on my dev machine so I can distribute the package to the other boxes.

[PhistucK]

This may help more -

http://www.chromium.org/developers/how-tos/api-keys

(I am not sure this is actually important)

☆PhistucK

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Renato de Sousa]

Those instructions are a bit out of date for how the Chromoting host currently works - there are some cases where it uses a new authentication model, which will require a different set of keys.

For Chromoting, you will need to create two sets of keys:

* a "Web Application" key (GOOGLE_CLIENT_ID_REMOTING, GOOGLE_CLIENT_SECRET_REMOTING), for the web application and the older authentication model for the host. You'll need to set the redirect URI for that key as indicated: https://chromoting-oauth.talkgadget.google.com/talkgadget/oauth/chrome-remote-desktop/dev

* an "Installed Application - Other" key (GOOGLE_CLIENT_ID_REMOTING_HOST, GOOGLE_CLIENT_SECRET_REMOTING_HOST), which is what the host uses when running with the new authentication model.

There is no way to pass both of these via the gyp include at the same time (it only allows you to pass a single key for everything), so I think the easiest way to set them in your personal build would be to remove the overrides from ~/.gyp/include.gypi and update the #defines in google_api/google_api_keys.cc directly.

(I apologize that this is currently a bit clunky right now - we're in the middle of some transitions for how we do auth and host registration, we expect that to be significantly cleaner once we're done)

--

[churnd]

Ah, well I'm glad you said something.  Saved me a lot of time.  :)  I don't think I can jump through all the hoops, seeing how I'm not familiar with the chromium code at all.

My main goal was just to get Chromoting host working on Ubuntu so I could log in anytime without having to start up the session locally.  What would you advise if that's my goal at this point?

[Paweł Hajdan, Jr.]

On Mon, Jun 16, 2014 at 9:43 PM, churnd <ch...@convorelay.com> wrote:

To be clear, I'm trying to build a .deb pkg for my Ubuntu systems so I can install the linux host service.  I'm trying to build this on my dev machine so I can distribute the package to the other boxes.

Please consider working with Ubuntu chromium-browser package maintainers to fix the problem for everyone.

Paweł