[YouTube-API] Re: Problem regarding displaying the application name in the Authorization Page

Hello Deepa,

I'm sorry, but I don't have any specific answers for those questions.
Whatever the YouTube API is doing should be standard for any Google
API, and I am not aware of any bugs in the GData client library
related to OAuth 1.0.

Cheers,
-Jeff Posnick, YouTube API Team
groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
@YouTubeDev

On Jan 13, 5:04 am, deepa shenoy <de...@robosoftin.com> wrote:
> Hi Jeffrey,
>
> After doing some R&D I came across the following content from the URLhttp://code.google.com/apis/accounts/docs/OAuth_ref.html#Parameters:
>
> "String identifying the application. This string is displayed to end
> users on Google's authorization confirmation page. For registered
> applications, the value of this parameter overrides the name set
> during registration and also triggers a message to the user that the
> identity can't be verified. For unregistered applications, this
> parameter enables them to specify an application name, In the case of
> unregistered applications, if this parameter is not set, Google
> identifies the application using the URL value of oauth_callback; if
> neither parameter is set, Google uses the string "anonymous"
>
> Authorization header of a GET or POST request. Use "Authorization:
> OAuth". All parameters listed above can go in the header, except for
> scope and xoauth_displayname, which must go either in the body or in
> the URL as a query parameter. The example below puts them in the body
> of the request.
>
> So, I tried setting the value of the parameter xoauth_displayname to
> 'My_App_Name':
> 1. When I tried this with registered Developer ID: Authorization page
> mentions Consumer Key instead of app name
> 2. When I tried with unregistered Developer ID: Authorization page
> mentions 'anonymous'
>
> Note:
> 1. I am using GData framework with OAuth 1.0 support.
> 2. The method 'tokenRequestKeys' in GDataOAuthAuthentication of this
> framework already included the key 'xoauth_displayname'.
> 3. I noticed that these parameters are included in authorization
> header of OAuthTokenRequest in the GData framework. But, the
> documentation mentions that the parameter 'xoauth_displayname' cannot
> go with authorization header.
>
> Is there any bug in the framework that I am using? Which revision of
> GData source I need to use.
> I checked the latest GData framework that supports OAuth2.0. Since I
> am in last state of the project I will not be able to integrate the
> major change [OAuth 1.0 interface to OAuth 2.0 interface]
>
> Kindle please help me and sorry for the huge content in the mail.
>
> Thanks and Regards,
> Deepa
>
> On Jan 13, 3:13 am, Jeffrey Posnick <je...@google.com> wrote:
>
>
>
>
>
>
>
> > Hello Deepa,
>
> >  The YouTube API team doesn't have any specific control over the OAuth
> > flow. It's a standard flow used for all the Google APIs, and the team
> > that designed the pages on the flow apparently thought it was
> > important to display that value.
>
> > Cheers,
> > -Jeff Posnick, YouTube API Team
> > groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> > @YouTubeDev
>
> > On Jan 10, 10:39 pm, deepa shenoy <de...@robosoftin.com> wrote:
>
> > > Jeffrey,
>
> > > Thank you for the quick response. Is this the behavior defined by the
> > > API team that consumer key is displayed in theauthorizationpage?
>
> > > Regards,
> > > Deepa
>
> > > On Jan 10, 10:46 pm, Jeffrey Posnick <je...@google.com> wrote:
>
> > > > Hello Deepa,
>
> > > >  I'm not sure that there's anything you could do here. The OAuthpage
> > > > isn't customizable in general.
>
> > > > Cheers,
> > > > -Jeff Posnick, YouTube API Team
> > > > groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> > > > @YouTubeDev
>
> > > > On Jan 9, 10:49 pm, deepa shenoy <de...@robosoftin.com> wrote:
>
> > > > > Hi All,
>
> > > > >  We are using GData framework with OAuth support (1.0) for user-login
> > > > > and using other Youtube APIs. We have obtained Developer ID,Client ID
> > > > > and Client Secret and are using these to access Youtube APIs.
> > > > > But we are encountering the followingproblem:
> > > > > Once the user logs in anauthorizationpageis put up which displays
> > > > > the Client ID in place of theapplicationname. Since user will not
> > > > > understand the client ID I would like to show myapplicationnamein
> > > > > theauthorizationpage.
>
> > > > > Note: I tried changing the OAuth version in GData framework to 2.0
> > > > > with no required output.
>
> > > > > What should I do to achieve this? Kindly could someone help me.
>
> > > > > Regards ,
> > > > > Deepa

--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.