Registering a web application

[vanderkerkoff]

Hello there

We're a google apps for education customer, lets say our domain name
is bongo.com.

I now need to start using Oauth within one of our web apps to
authorise users.

I've enabled the consumer key, and allowed access to all API's on the
SetupOauth page in the cpanel.

I now need to add an Authorized API Client, the website in question,
users.bongo.com.

When I try to add users.bongo.com that it tells me that "This client
name has not been registered with Google yet."

So I go the help page at http://code.google.com/apis/accounts/docs/RegistrationForWebAppsAuto.html

This page describes why you would want to register a web based
application, then describes the different levels of registration of a
web application, and then gives you instructions on how to register a
new domain. I don't want to register a new domain do I?

Anyway, I go to the page in my cpanel, I can see our domain that is
registered, bongo.com, and some options to add other domains. I
really start to panic now, I don't want to do this.

So, return to the ManageOauthClients page, and in the client name I
add bongo.com, and give it access to a Scope and save it.

My question is this.

Is that all I need to do in order to send and receive OAuth details
from USERS.bongo.com?

If there's anything else I need to do, can someone please let me know?

[Gunjan Sharma]

Hello Vanderkerkoff

I am not sure if I got your question right but I will try to write your problem in my words.

So I think you want to use OAuth to authorize your domain users for an app that you own.

If that is the case then you will have to build your own OAuth supported app which will authorize users using it.  Enabling the consumer key, and allowed access to all API's on the SetupOauth page in the cpanel will only allow you to authorize the Google Apps apis using OAuth.

Even registering the client helps Google apis to know that you have authorized this client to access Google Apps apis on your behalf.

In summary your application will have to support OAuth to authorize your domain users.

As a work around your application can always make the user to login into there accounts before they can access the app and once they login you can get there email address and see if it belongs to your domain.

Thanks

Gunjan Sharma

[vanderkerkoff]

Hi Gunjan

"So I think you want to use OAuth to authorize your domain users for
an app that you own. "

Yes. The app will reside at users.bongo.com, I will write the oauth
code in the app and authorize our domain users and pull down some data
from that users calendar feed.

My question is do I have to do anything else or will the app at
users.bongo.com be able to authenticate via oauth?

In my ManageOauthClients page in cpanel, the only authorized client is
bongo.com, not users.bongo.com.

Is that enough to enable the app at users.bongo.com to use oauth to
authenticate? If so, then anything.bongo.com can use oauth to
authenticate with the google API's, that's not a problem though, but
as I'm trying to test I need to be certain that I can authenticate
from test.bongo.com as my test machine is test.bongo.com.

I'm more than likely reading something incorrectly, any help is
greatly appreciated.

V

On Jan 14, 7:11 am, Gunjan Sharma <gunjansha...@google.com> wrote:
> Hello Vanderkerkoff
>
> I am not sure if I got your question right but I will try to write your
> problem in my words.
> So I think you want to use OAuth to authorize your domain users for an app
> that you own.
>
> If that is the case then you will have to build your own OAuth supported

> app which will authorize users using it.  *Enabling the consumer key, and
> allowed access to all API's on the SetupOauth page in the cpanel* will only