#360 closed enhancement (fixed)

Implement MSN SOAP authentication

Reported by: ruicruz@… Owned by: wilmer
Priority: normal Milestone:
Component: MSN Version: 1.0.3
Keywords: Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:



I am using a new msn account on im.bitlbee and testing.bitlbee and it dosnt seem to connect correctly.

I am getting this (from testing): <@root> msn - Couldn't log in: Error during Passport authentication (HTTP error: 401 Unauthorized)

This dosnt seem related to me, since I have another account sign in.

I can access my account with EXACT information on Microsoft's MSN client.

So... any fix or solution for this?

Also I've tryied passwords in plain-text, dosnt work too.


Attachments (0)

Change History (8)

comment:1 Changed at 2008-02-13T21:53:50Z by wilmer

Priority: blockernormal
Summary: Problem with new MSN accountProblem with long MSN Messenger passwords

We investigated, it looks like there's a problem with long (>10 chars) passwords. Making the password shorter fixes the problem. Pidgin's also unable to login with such a long password.

This is pretty strange, I verified that BitlBee is sending the right thing, and it really is. I suppose this method of Passport authentication is deprecated and doesn't support long passwords, for some very odd reason...

For now, people should probably just choose shorter password. It's instant messaging, not a bank account. :-P

comment:2 Changed at 2008-02-13T21:54:12Z by wilmer

Component: BitlBeeMSN
Owner: set to wilmer

comment:3 Changed at 2008-02-14T11:29:22Z by Join

Ok, with less chars it is fixed.



comment:4 Changed at 2008-02-14T18:31:26Z by wilmer

Gotcha. Miranda works properly. They're doing SOAP authentication with an überbloated XML blob, apparently MSN/Passport does support longer passwords that way. Gotta copy that. :-)

comment:5 Changed at 2008-02-14T18:54:42Z by wilmer for more information. I wonder if this will work for MSNP9 (or whatever BitlBee uses)...

comment:6 Changed at 2008-02-16T23:16:28Z by wilmer

Okay, I mostly implemented this now. The error/redirection handling isn't there yet, but it logs in properly. Will probably add that tomorrow.

It does look like this didn't fix the long-password issue. Not sure about that though. :-(

Even if it doesn't fix that problem, implementing this was probably still a good idea. Sooner or later Microsoft would probably drop Passport 1.4 support.

comment:7 Changed at 2008-02-16T23:38:35Z by wilmer

Summary: Problem with long MSN Messenger passwordsImplement MSN SOAP authentication
Type: defectenhancement

So apparently MSN doesn't support passwords that have more than 16 characters. It doesn't even allow you to fill in longer passwords on their webform. Most likely you copy-pasted your password from a generator in your browser and didn't notice that (like I did for two days).

Unfortunately the Passport authentication code doesn't chop off extra characters so the verification will fail. If you chop them off yourself, you should be able to log in. With both the old and the new code.

This problem's solved, so I'll hijack this ticket for finishing that SOAP authentication. :-P

comment:8 Changed at 2008-02-17T11:28:25Z by wilmer

Resolution: fixed
Status: newclosed

Okay, SOAP is implemented, and also I made it truncate >16 char passwords so this problem should be gone.

Modify Ticket

as closed The owner will remain wilmer.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.