Error: 403: OK (YouTube API Settings)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Log into /admin and then "configuration"
2. In "YouTube API Settings" try to link the YT account
3. Then in Youtube "allow access"
4. The system redirects to /admin/PersistAuthSubToken?token= with Error: 403:

What is the expected output? What do you see instead?
I expect seeing my YT account linked to the YTD. Instead I saw Error: 403: OK

What version of the product are you using? On what operating system?
Last release (checkout was on March 15).

Please provide any additional information below.
- I have successful test this on my local machine using the 1.4.2 SDK (1.4.0 
don't even start on local).
- I have also try SDK 1.3.8 
- I'm using eclipse helios

Original issue reported on code.google.com by soychil...@gmail.com on 15 Mar 2011 at 10:38

[GoogleCodeExporter]

did anyone fix this issue?

Original comment by Areyouli...@gmail.com on 17 Mar 2011 at 2:58

[GoogleCodeExporter]

Yes, I also need a fix for this one.

Original comment by funlikel...@gmail.com on 20 Mar 2011 at 10:53

[GoogleCodeExporter]

Can you all confirm that you have properly registered your production App 
Engine domain for AuthSub following the instructions at

  http://code.google.com/p/youtube-direct/wiki/GettingStarted#Registering_your_website_for_AuthSub

(Ensure that you are using "http" instead of "https" when you specify your 
domain's URL.)

Original comment by api.je...@gmail.com on 21 Mar 2011 at 2:16

[GoogleCodeExporter]

Original comment by api.je...@gmail.com on 21 Mar 2011 at 2:17

• Changed state: Started

[GoogleCodeExporter]

Registering with AuthSub now allows me to access to the admin page. Actually I 
found that solution like 2 days ago but there is something else...

When you already have this running, with the proper AuthSub (basic), in the 
admin section there is no issues but when you as any user want to upload new 
content using the embed code a not loged user gets the same error (Error: 403: 
OK) when this users gives permission to the app. The weird thing is that if you 
go back and refresh the page you are logged in the system and you can send 
content, and even if you are already loged in youtube the app don't ask for 
permission or there is any error.

I think that perhaps I need to use the advanced AuthSub config, where you 
set-up certificates.

Original comment by soychil...@gmail.com on 21 Mar 2011 at 4:21

[GoogleCodeExporter]

I'm also having this exactly same issue!

Original comment by rodolfo....@gmail.com on 22 Mar 2011 at 8:47

[GoogleCodeExporter]

Setting up certificates shouldn't be necessary.

Which web browser are you seeing this with?

Could you point me to a web page that hosts your YTD embed so that I could try 
to reproduce the behavior you're seeing? I also might need you to look up any 
errors that are present in the App Engine logs, but let me try to reproduce the 
issue first.

Original comment by api.je...@gmail.com on 22 Mar 2011 at 9:00

[GoogleCodeExporter]

Actually, I've been able to reproduce this myself now, and am following up 
internally to see what changed with the AuthSub session token exchange process 
that would cause this.

Original comment by api.je...@gmail.com on 23 Mar 2011 at 6:27

• Changed state: 4074670

[GoogleCodeExporter]

I have test this with Safari, Opera, Firefox and Chrome (all on Snow Leopard).
Safari: Error: 403: OK
Opera: Stop and says that the page has been redirected to "." (single dot).
Firefox: Error: 403: OK
Chrome: Error 311 (net::ERR_UNSAFE_REDIRECT): Unknow Error.

Original comment by soychil...@gmail.com on 24 Mar 2011 at 3:20

[GoogleCodeExporter]

This issue looks to be the result of someone (inadvertently?) registering the 
top-level appspot.com domain for AuthSub. The relevant teams within Google are 
looking into how this happened and will hopefully undo it soon. In the 
meantime, explicitly registering your site as described at

  http://code.google.com/p/youtube-direct/wiki/GettingStarted#Registering_your_website_for_AuthSub

should work around the issue.

Original comment by api.je...@gmail.com on 24 Mar 2011 at 3:24

[GoogleCodeExporter]

Hello,

By "explicitly registring", do you mean use the "secure" AuthSub ?

I'm new to youtube direct and I'm stuck on this.

Thx

Original comment by mediacit...@souslebaobab.com on 27 Mar 2011 at 10:59

[GoogleCodeExporter]

"Secure" AuthSub shouldn't be necessary, but registering your appspot.com 
domain at https://www.google.com/accounts/ManageDomains is needed right now.

I have recently spoken to the folks within Google responsible for the AuthSub 
infrastructure and they've acknowledged the problem and are working on a 
solution. This issue should clear itself up once that happens, but registering 
your domain is a good idea anyway.

Original comment by api.je...@gmail.com on 28 Mar 2011 at 2:59

[GoogleCodeExporter]

Hi,

In that case, how can I upload the google validation file to my appspot.com 
domain?

Thx

Original comment by mediacit...@souslebaobab.com on 28 Mar 2011 at 7:31

[GoogleCodeExporter]

The easiest method is adding the <meta> tag to the <head> element in your copy 
of the war/index.html file, and then redeploy the project to App Engine.

Original comment by api.je...@gmail.com on 28 Mar 2011 at 9:45

[GoogleCodeExporter]

The underlying issue was just fixed by the team responsible for AuthSub, so 
registering your App Engine instance for AuthSub should no longer be necessary 
(but it's still a good practice).

Original comment by api.je...@gmail.com on 29 Mar 2011 at 3:43

• Changed state: Fixed

[GoogleCodeExporter]

Sorry to bother again, but It seems that the issue is still there, and this 
time is not on the admin access but in the user action.

I have just generate the html/js code for embed with the call to action (upload 
button) and try to emulate the normal behavior of any user... I take this html, 
log in as different user, and when I grant permission there is the infamous 403 
was still there (in some browsers there is error output, blank page, etc)

And again, I'm using the basic AuthSub. This time I will attach the embedable 
html so you can taste directly and not try to figure it.

Thanks in advance.

Original comment by soychil...@gmail.com on 29 Mar 2011 at 9:55

Attachments:

• yt.html

[GoogleCodeExporter]

I just tried using your embed code on my own page and authentication worked 
fine.

One thing to note is that you need to make sure you have a YouTube API 
developer key configured in your YouTube Direct admin panel, as this will 
greatly reduce the chance that you might experience a random failure due to 
YouTube API quota limitations. Do you have your developer key entered in the 
admin panel?

Original comment by api.je...@gmail.com on 29 Mar 2011 at 10:05

[GoogleCodeExporter]

Oh, my mistake... I forgot to test outside localhost. Thanks for all!

Original comment by soychil...@gmail.com on 29 Mar 2011 at 10:30

[GoogleCodeExporter]

I am trying to upload an aquasoft slideshow and I keep getting error code 403. 
please help! 

Original comment by margetad...@gmail.com on 25 Jul 2011 at 1:53

[GoogleCodeExporter]

I'm not sure what an aquasoft slideshow is. How is this related to YouTube 
Direct? At which stage in the YouTube DIrect flow does the error occur?

Original comment by api.je...@gmail.com on 25 Jul 2011 at 10:02

[GoogleCodeExporter]

Hi, I got exactly the same problem and I fixed it!
This is the solution: I just make one channel/username in youtube(it 
automatically associate with my google account).

Hope this will help all other users that have the same problem.

Original comment by pubmuc.z...@googlemail.com on 12 Mar 2012 at 3:43