[YouTube-API] Re: So how to authenticate now?

Hello Dennis,

So yes, I understand that frustration regarding the upload flow using
OAuth 2 and I'm personally disappointed that this hasn't been fixed
yet. All I can say is that the correct folks have been notified
internally and the need to address the issue is clear—it's just a
question of getting that code completed and pushed out.

Regarding a way to check if a token is still valid, you could use the
service described at

https://developers.google.com/accounts/docs/OAuth2UserAgent#validatetoken

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


On Apr 24, 1:43 am, Dennis Fischer <chaosking0...@googlemail.com>
wrote:
> Hey,
>
> yes, that's the technical issue I was talking about. I already tried using
> OAuth 2 in my application.
> Migration was difficult because I was using ClientLogin. I experienced
> multiple problems:
>
>    1. I've sent the user to the OAuth request page. He accepted and entered
>    the generated code in my application.
>    However, google didn't return an refresh and access token after that
>    step. It took like 2 hours until my application was "activated" and the
>    same code started working.
>    2. The user started with an OAuth access token an upload. The metadata
>    was sent (200:OK). The video was uploaded with the same access token (it
>    should have been valid! The upload took about 1 minute) On the last PUT
>    Request Response Code 401 (Uploading from unauthorized ...) was returned.
>    In fact: The metadata upload "system"  seems to be broken for a while. The
>    validation of metadata and the permission validation isn't taking place.
>    Posting Bad XML Metadata returns a valid upload url, but will return error
>    400:Bad Request on the last PUT.
>    There seems to be the same problem with authorization: POSTing valid
>    metadata without authorization returns an upload url and fails on the last
>    PUT Request with error 401.
>
> Well, that should explain why I'm not satisfied with googles oauth 2
> implementation. I've already worked with facebooks oauth 2 and it worked
> immediately and I don't have to worry about access token expiration.
>
> 3. Where / how can I check if an access token is still valid? Facebook,
> twitter.. all offer you some urls like /feed/me or /help/test/ where you
> can easily check the validity. I couldn't find any appropriate so far for
> google.
>
> Regards,
>
> Dennis Fischer
> Am Montag, 23. April 2012 23:31:36 UTC+2 schrieb Jeffrey Posnick:
>
>
>
>
>
>
>
>
>
> > Hello Dennis,
>
> >  We currently recommend OAuth 2. In fact, all of the other methods of
> > authentication are deprecated:
>
> >http://googledevelopers.blogspot.com/2012/04/changes-to-deprecation-p...
>
> > (The YouTube API documentation is being updated to reflect this.)
>
> >  There is an unfortunate situation where using OAuth 2 when performing
> > an upload can lead to a failure if the upload takes a while and the
> > OAuth 2 access token expires before the upload is complete. We're
> > actively working to get that situation addressed, though. Is that the
> > "technical issue" that you are referring to, or was there something
> > else that was preventing you from using OAuth 2?
>
> > Cheers,
> > -Jeff Posnick, YouTube API Team
> > groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> > @YouTubeDev
>
> > On Apr 22, 1:33 pm, Dennis Fischer <chaosking0...@googlemail.com>
> > wrote:
> > > Hey,
>
> > > Currently I'm using ClientLogin, however I want to finally migrate to
> > OAuth.
> > > As I've read, OAuth 2.0 is experiencing some technical issues.
> > > AuthSub was suggested as a replacement, however this would take me lots
> > of
> > > code to write.
> > > OAuth 1.0 is missing many information. Where can I register an apikey
> > and
> > > apisecret for installed Applications?
>
> > > So whichever type I select, it's not working as I want.
> > > Any help?
>
> > > Regards,
>
> > > Dennis Fischer

--
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.