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-policies-and-api.html
(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.
No comments:
Post a Comment