I am developing an app that uses OAuth authorization to get access to the Myspace API.

I have now switched from calling the app from our development server, to calling it from the production server. While I was calling from the development server, the callback worked correctly. After the user had signed in, they were returned to the correct page on the development server.

Here's what the call looks like:

    http://api.myspace.com/authorize?oauth_token=...==&oauth_callback=http%3A%2F%2Fblip.tv%2Fprefs%2Fmyspace_update

(I've elided the oauth_token value to save space).

Since I switched to making the call from the production server - which is located in a different domain - the callback no longer works. The Myspace authorization page does not display any error, but simply reloads.

I assumed that this was because I had the wrong domain set in the "External Site Settings" part of the application specification (our development and production servers are in different domains). I corrected this, but the problem continues.

Does it take a certain amount of time for Myspace to register that the External Site Settings have changed? Or is it being held up because I've just changed the status from Development to Published, and it's still marked as Pending?

 Additional data point: it looks as if it has nothing to do with the Pending state of the app.

 I've now created two apps, which are identical except for the External Site Settings (one is set to allow callbacks to our development domain, the other to allow callbacks to our production domain).

Calling back to our development domain works perfectly; calling back to our production domain fails; the /authorize page just reloads.

Barring some configuration error that I'm not seeing, it looks as if Myspace doesn't like to call back to 'blip.tv', whereas it's more than happy to call back to 'mydev.pokkari.net' (the development domain).

 Hey there, let me check this out.
Rhonda

 Is this an offsite application or MySpaceID application? Also, what is the app id?

 Was this ever resolved?  I'm seeing a similar problem.

Mike:

 Was this ever resolved?  I'm seeing a similar problem.

Is this an offsite application or MySpaceID application? Also, what is the app id?

rondata@myspace:

Is this an offsite application or MySpaceID application? Also, what is the app id?

Our app is offiset.  App ID is 129526.

 I have the same problem. I have an offsite application and I don't know what writte in the oauthcallback. Can somebody help me?

Have you resolved this issue and how? I meet a same problem. When signin with the user ID who is not the owner of the APP's consumer_secret, the call back does not work. Only when signin with the owner ID, the call back can take effect.

When I choose continue, the call back url can tacke effect. But in case I choose 'It is not me' and signin with other user ID, the call back

does not work. Why?

Answer someone!!!..plsssss 

 Make sure you're using the MySpaceID SDKs

This has been a public service anouncement :)

rondata:

 Make sure you're using the MySpaceID SDKs

This has been a public service anouncement :)

This does not fix the problem. Using the myspaceid sdk oauth example I get the same problem. It also redirects to this:

http://oob/?oauth_problem=oauth_problem%253Dparameter_rejected%252C%2520oauth_parameters_rejected%253DExternal%252520Domain%26oauth_problem_advice%253D%255BExternal%2520Domain%255D%2520or%2520%255Boauth_callback%255D%2520uri%2520is%2520not%2520set.&oauth_verifier=0ced7eb2-26f2-44b6-bd32-929180299f2c

 What is going on here.

 I alsohave this oob redirect problem

 Hi

My application ID is 152276 . I am using Myspace SKD. When i am login own owner userid, its callback to currect url. but when i using other userid and password its not call back to callback url. Its goes to myspace-home. How to fix this problem. Pls help me.