I use MySpaceID SDK (.net c#) to develop my app. It is based on one of the samples from the SDK. Everything with MySpaceID worked just fine for several months. As I add new minor features to the app I republish the app to my site web server. The last time I published the app MySpaceID stopped working - when I enter login/password it brings me back to Login page of my site and I get AuthenticationStatus = Failed. Why? I didn't change neither any settings of my App at MySpace, nor any code related to MySpaceID in C# code. Consumer key and secret are correct, I use myspace account which is in developer list.

Another question: why can't I get exception message? I can't easily work out the issue myself.

Here are some line from my log:

26 Oct 2009 04:10:14 DEBUG [Logger] openid.GetResponse() status: Failed
26 Oct 2009 04:10:14 DEBUG [Logger] openid.GetResponse() exception: DotNetOpenAuth.Messaging.Bindings.ExpiredMessageException: The message expired at 10/26/2009 4:09:25 AM and it is now 10/26/2009 4:10:14 AM.
   at DotNetOpenAuth.Messaging.Bindings.StandardExpirationBindingElement.PrepareMessageForReceiving(IProtocolMessage message) in C:\prj\Sna\SocialNetworkAdv\DEV\trunk\Development\Source\SocialNetworkAdv\ThirdParty\myspaceid-csharp-sdk\source\dotnetopenid\src\DotNetOpenAuth\Messaging\Bindings\StandardExpirationBindingElement.cs:line 92
   at DotNetOpenAuth.Messaging.Channel.VerifyMessageAfterReceiving(IProtocolMessage message) in C:\prj\Sna\SocialNetworkAdv\DEV\trunk\Development\Source\SocialNetworkAdv\ThirdParty\myspaceid-csharp-sdk\source\dotnetopenid\src\DotNetOpenAuth\Messaging\Channel.cs:line 759
   at DotNetOpenAuth.OpenId.ChannelElements.OpenIdChannel.VerifyMessageAfterReceiving(IProtocolMessage message) in C:\prj\Sna\SocialNetworkAdv\DEV\trunk\Development\Source\SocialNetworkAdv\ThirdParty\myspaceid-csharp-sdk\source\dotnetopenid\src\DotNetOpenAuth\OpenId\ChannelElements\OpenIdChannel.cs:line 137
   at DotNetOpenAuth.Messaging.Channel.ReadFromRequest(HttpRequestInfo httpRequest) in C:\prj\Sna\SocialNetworkAdv\DEV\trunk\Development\Source\SocialNetworkAdv\ThirdParty\myspaceid-csharp-sdk\source\dotnetopenid\src\DotNetOpenAuth\Messaging\Channel.cs:line 319
   at DotNetOpenAuth.OpenId.RelyingParty.OpenIdRelyingParty.GetResponse(HttpRequestInfo httpRequestInfo) in C:\prj\Sna\SocialNetworkAdv\DEV\trunk\Development\Source\SocialNetworkAdv\ThirdParty\myspaceid-csharp-sdk\source\dotnetopenid\src\DotNetOpenAuth\OpenId\RelyingParty\OpenIdRelyingParty.cs:line 315


Please help

Is there any help? This issue is quite odd. I have two identical widgets set up for two identical sites but of different domains. For one of them MySpaceID login suddenly stopped working, for the other it still works. As I told I didn't change any widget settings, environment on my servers is the same, application version is identical. Is it possible that at MySpace there is some kind of a black list of 'bad' IPs where my IP got? I can't get any diagnostics why I can't log in as the exception message is always expired when I try to get it (!).

I'm very disappointed with such MySpace support... We have developed an app and are ready to publish it, but unstable platform (or maybe just lack of decent support) prevents us from doing it. This affects our business plans. During last couple of weeks MySpaceID login's been working only from time to time... A week ago it broke and I guessed wheather it was something in our code or not. Then, I don't know how, it started working again. Today again it's not working - now I'm sure no changes in our code. And in addition to all, as written above, there's no any diagnostics available except for eternally expired error messages.

Please give us some hints

Hey FalconD,

Can you paste a fiddler response back from the server when this happens? http://www.fiddler2.com/fiddler2/
We have not made any changes to the OpenID project in awhile. New and exciting endpoints are coming from MDP.

-Thanks
-V

Here it is:

HTTP/1.1 302 Found
Cache-Control: no-cache, must-revalidate, proxy-revalidate
Pragma: no-cache
Content-Length: 0
Expires: -1
Location: http://www.famose.com/MySpace/Login.aspx?openid.ns=http%3a%2f%2fspecs.openid.net%2fauth%2f2.0&openid.ns.oauth=http%3a%2f%2fspecs.openid.net%2fextensions%2foauth%2f1.0&openid.oauth.request_token=q0DyDTncmE0eiezgX9Hd0%2bEildc98xUd8aI7K2y7I7iGOeSsT3ev0FY1Ppqo5erCkclPaK928SlpOnJBV7r8KgV7nGmQ1tTVEX5VeIf5dhyBHwuKVPcbMsYvx4Aws2sX&openid.oauth.verifier=14e6854b-8bc4-45a8-a402-cc4c00dfb2c3&openid.mode=id_res&openid.identity=http%3a%2f%2fwww.myspace.com%2fsocadvcustomer&openid.return_to=http%3a%2f%2fwww.famose.com%2fMySpace%2fLogin.aspx&openid.claimed_id=http%3a%2f%2fwww.myspace.com%2fsocadvcustomer&openid.op_endpoint=http%3a%2f%2fapi.myspace.com%2fopenid&openid.response_nonce=2009-11-10T08%3a01%3a45Z%3eo7%251.1%22&openid.assoc_handle=%7b%7bHMAC-SHA512%7d%7b1257840105.74124%7d%7bCV7C7A%3d%3d%7d&openid.signed=ns.oauth%2coauth.request_token%2coauth.verifier%2creturn_to%2cidentity%2cclaimed_id%2cop_endpoint%2cresponse_nonce%2cassoc_handle&openid.sig=dDOEWNUitGlyxFNS16W2wg5k0USHaL33kQKm5QCglfsxP3V4UegfOnlGnTK2iDK13%2bbNRIWtQC8viWDEXpKM4A%3d%3d
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Server: e7ea7fdb63756db67b2f9872ab36762a395344316549c08c
Date: Tue, 10 Nov 2009 08:01:45 GMT

And here is the same response from our test server (with different widget set up), where everything still works fine:

HTTP/1.1 302 Found
Cache-Control: no-cache, must-revalidate, proxy-revalidate
Pragma: no-cache
Content-Length: 0
Expires: -1
Location: http://www.alterengine.com/MySpace/Login.aspx?openid.ns=http%3a%2f%2fspecs.openid.net%2fauth%2f2.0&openid.ns.oauth=http%3a%2f%2fspecs.openid.net%2fextensions%2foauth%2f1.0&openid.oauth.request_token=AR61xd9RU96haqFEbM%2bCNhyqNI%2f6pD8CCZEfk9DW4H%2boWP3EaZqWXJbzlgovY5w15V8AK5GN%2bFXLelYjDk0v6ide8qxVrhh2kkyjForQ5gwyJv9dZJsJfWQxbpHV08jO&openid.oauth.verifier=ef8fb591-4952-47aa-9893-2ddbe4ca97bc&openid.mode=id_res&openid.identity=http%3a%2f%2fwww.myspace.com%2fnvsokolov&openid.return_to=http%3a%2f%2fwww.alterengine.com%2fMySpace%2fLogin.aspx&openid.claimed_id=http%3a%2f%2fwww.myspace.com%2fnvsokolov&openid.op_endpoint=http%3a%2f%2fapi.myspace.com%2fopenid&openid.response_nonce=2009-11-10T08%3a14%3a37Zg064%24s%2fv&openid.assoc_handle=%7b%7bHMAC-SHA512%7d%7b1257840877.45737%7d%7btmLaSQ%3d%3d%7d&openid.signed=ns.oauth%2coauth.request_token%2coauth.verifier%2creturn_to%2cidentity%2cclaimed_id%2cop_endpoint%2cresponse_nonce%2cassoc_handle&openid.sig=51Vm6YSCk4N6q5X5Cm%2bfbCA1A9QUI6PBXG700opVNesVTTcdT5roz7nn58M%2f6SMDlYztkRpn40FOrBO1Xh1F4Q%3d%3d
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Server: a2318d0d388e9b582eee2e7a2383eb1c7d75c6fd98338c26
Date: Tue, 10 Nov 2009 08:14:37 GMT

Today it again works... And again I have not changed anything. Did MySpace do something about my issue or is it just a coincidence?

It's not the first time when it suddenly starts or stops working... we'd like to know the reason and wheather this may occur again because otherwise it'll just be not reliable enough platform and some doubts if we should continue developing applications at MySpace.

Hi FalconD,

 This could have been due to a code push which was then rectified when functionality was adversely affected. We apologize for this inconvenience.

 

thanks,

Joel