search

TReKiE / msnp-sharp

Automatically exported from code.google.com/p/msnp-sharp
0 stars 0 forks source link

Authentication failed: The requested feature is not implemented #126

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Using Mono version 2.0.1, and attempting to connecting to MSN
2.
3.

What is the expected output? What do you see instead?
I expect to be logged in, instead
Connection Established.
Authentication failed, check your account or password. :The requested
feature is not implemented.. See innerexception for detail.
  at MSNPSharp.SingleSignOn.Authenticate (MSNPSharp.MSNTicket msnticket,
Boolean async) [0x00000] 
  at MSNPSharp.SingleSignOnManager.Authenticate (MSNPSharp.NSMessageHandler
nsMessageHandler, System.String policy) [0x00000] 
  at MSNPSharp.NSMessageHandler.OnUSRReceived (MSNPSharp.Core.NSMessage
message) [0x00000] 

What version of the product are you using? (MSNPSharp, OS, Mono etc.)
I've tried  2.5.7 and latest svn. os is linux, Mono 2.0.1

Please provide any additional information below.

Original issue reported on code.google.com by xdieyoun...@gmail.com on 10 Aug 2009 at 4:11

GoogleCodeExporter commented 9 years ago 
Hi,
Would you please debug into the library and show us the stacktrace? It's hard 
to 
locate the problem because I haven't got Linux.

Original comment by freezing...@gmail.com on 10 Aug 2009 at 9:42

GoogleCodeExporter commented 9 years ago 
I hope this is right,
EXCEPTION handling: NotImplementedException
EXCEPTION handling: MSNPSharpException
Authentication failed, check your account or password.:  
at System.Net.HttpWebRequest.set_AutomaticDecompression (DecompressionMethods 
value)
[0x00000] 
  at (wrapper remoting-invoke-with-check)
System.Net.HttpWebRequest:set_AutomaticDecompression 
(System.Net.DecompressionMethods)
  at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebRequest (System.Uri
uri) [0x00000] 
  at System.Web.Services.Protocols.SoapHttpClientProtocol.GetWebRequest (System.Uri
uri) [0x00000] 
  at System.Web.Services.Protocols.SoapHttpClientProtocol.GetRequestForMessage
(System.Uri uri, System.Web.Services.Protocols.SoapClientMessage message) 
[0x00000] 
  at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke (System.String
method_name, System.Object[] parameters) [0x00000] 
  at
MSNPSharp.MSNWS.MSNSecurityTokenService.SecurityTokenService.RequestMultipleSecu
rityTokens
(MSNPSharp.MSNWS.MSNSecurityTokenService.RequestMultipleSecurityTokensType
RequestMultipleSecurityTokens1) [0x00000] 
  at (wrapper remoting-invoke-with-check)
MSNPSharp.MSNWS.MSNSecurityTokenService.SecurityTokenService:RequestMultipleSecu
rityTokens
(MSNPSharp.MSNWS.MSNSecurityTokenService.RequestMultipleSecurityTokensType)
  at MSNPSharp.SingleSignOn.Authenticate (MSNPSharp.MSNTicket msnticket, Boolean
async) [0x00000]

Original comment by xdieyoun...@gmail.com on 10 Aug 2009 at 3:02

GoogleCodeExporter commented 9 years ago 
Apparently its a bug in mono, fixed in 2.4.1 (2.0.1 is the latest in buntu 
repo's :() 
http://lists.ximian.com/pipermail/mono-list/2009-May/042442.html is a link if 
anyones
curious.

Original comment by xdieyoun...@gmail.com on 11 Aug 2009 at 4:36

GoogleCodeExporter commented 9 years ago 
Upgraded to 2.4.3(mono) and now i seem to be getting:
EXCEPTION handling: ArgumentException
EXCEPTION handling: ArgumentException
EXCEPTION handling: NotImplementedException
Connecting..
EXCEPTION handling: ConfigurationErrorsException
EXCEPTION handling: ConfigurationErrorsException
Connection Established
EXCEPTION handling: ObjectDisposedException
Connection Established
EXCEPTION handling: ConfigurationErrorsException
EXCEPTION handling: UnauthorizedAccessException
EXCEPTION handling: SoapException
EXCEPTION handling: MSNPSharpException
Authentication failed, check your account or password.:  at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReceiveResponse
(System.Net.WebResponse response, 
System.Web.Services.Protocols.SoapClientMessage
message, System.Web.Services.Protocols.SoapExtension[] extensions) [0x00000] 
  at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke (System.String
method_name, System.Object[] parameters) [0x00000] 
  at
MSNPSharp.MSNWS.MSNSecurityTokenService.SecurityTokenService.RequestMultipleSecu
rityTokens
(MSNPSharp.MSNWS.MSNSecurityTokenService.RequestMultipleSecurityTokensType
RequestMultipleSecurityTokens1) [0x00000] 
  at (wrapper remoting-invoke-with-check)
MSNPSharp.MSNWS.MSNSecurityTokenService.SecurityTokenService:RequestMultipleSecu
rityTokens
(MSNPSharp.MSNWS.MSNSecurityTokenService.RequestMultipleSecurityTokensType)
  at MSNPSharp.SingleSignOn.Authenticate (MSNPSharp.MSNTicket msnticket, Boolean
async) [0x00000] Authentication Failure. aSee innerexception for detail.

Original comment by xdieyoun...@gmail.com on 11 Aug 2009 at 5:52

GoogleCodeExporter commented 9 years ago 
Authentication failed, check your account or password.:
  at System.Web.Services.Protocols.SoapHttpClientProtocol.ReceiveResponse
(System.Net.WebResponse response, 
System.Web.Services.Protocols.SoapClientMessage
message, System.Web.Services.Protocols.SoapExtension[] extensions) [0x0022c] in
/build/buildd/mono-2.4.2.3+dfsg/mcs/class/System.Web.Services/System.Web.Service
s.Protocols/SoapHttpClientProtocol.cs:351

  at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke (System.String
method_name, System.Object[] parameters) [0x000b8] in
/build/buildd/mono-2.4.2.3+dfsg/mcs/class/System.Web.Services/System.Web.Service
s.Protocols/SoapHttpClientProtocol.cs:379

  at
MSNPSharp.MSNWS.MSNSecurityTokenService.SecurityTokenService.RequestMultipleSecu
rityTokens
(MSNPSharp.MSNWS.MSNSecurityTokenService.RequestMultipleSecurityTokensType
RequestMultipleSecurityTokens1) [0x00000] in
/home/ikex/Projects/PureMSN/MSNP-Sharp/MSNPSharp/Web
References/MSNWS.MSNSecurityTokenService/Reference.cs:124 
  at (wrapper remoting-invoke-with-check)
MSNPSharp.MSNWS.MSNSecurityTokenService.SecurityTokenService:RequestMultipleSecu
rityTokens
(MSNPSharp.MSNWS.MSNSecurityTokenService.RequestMultipleSecurityTokensType)
  at MSNPSharp.SingleSignOn.Authenticate (MSNPSharp.MSNTicket msnticket, Boolean
async) [0x00264] in 
/home/ikex/Projects/PureMSN/MSNP-Sharp/MSNPSharp/SingleSignOn.cs:623 
Authentication Failure

Original comment by xdieyoun...@gmail.com on 11 Aug 2009 at 5:57

GoogleCodeExporter commented 9 years ago 
That means your password is incorrect. Are you sure you've entered the right 
account 
and password?

Original comment by freezing...@gmail.com on 11 Aug 2009 at 2:09

GoogleCodeExporter commented 9 years ago 
Yep i've tried 2 accounts (Active one i use currently and an old one)

Original comment by akto...@gmail.com on 12 Aug 2009 at 3:24

GoogleCodeExporter commented 9 years ago 
The fix 1 (Singlesignon.cs):

MSNSecurityServiceSoapClient securService = new MSNSecurityServiceSoapClient(); 
//It
is a hack
            try
            {
                securService.EnableDecompression = true;
            }
            catch (NotImplementedException)
            {
            }

The fix 2 (MsnService.cs):

if (service != null)
            {
                try
                {
                    service.EnableDecompression = true;
                }
                catch (NotImplementedException)
                {
                }

                if (asyncObject != null && asyncObject.IsAsync)
                {
                    lock (asyncStates)
                        asyncStates[service] = asyncObject;
                }
            }

Original comment by hepha...@gmail.com on 12 Aug 2009 at 4:18

GoogleCodeExporter commented 9 years ago 
Compression loads your addressbook faster 80-90% for web requests. I think, it 
hasn't
implemented in mono yet.

Original comment by hepha...@gmail.com on 12 Aug 2009 at 4:22

GoogleCodeExporter commented 9 years ago 
Ah, thanks.

Original comment by freezing...@gmail.com on 13 Aug 2009 at 11:52

GoogleCodeExporter commented 9 years ago

Original comment by hepha...@gmail.com on 8 Sep 2009 at 9:24

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r1319.

Original comment by hepha...@gmail.com on 9 Oct 2009 at 8:45