skype4pidgin
skype4pidgin copied to clipboard
EionRobb
Failed getting magic T value, after MS shut down the last MSN servers?
The plugin was working fine, until MS shut down the latest msn servers, a few days ago. Could it be that they changed, also, something on the skype ones? I tried to follow the diagram, but I couldn't find the "2 factor authentication" option, unless it's the blank option on the plugin advanced tab (which I changed without any results). I'm using pidgin v2.12 and skypeweb v1.4.
2 factor authentication is not a setting in this plugin https://en.wikipedia.org/wiki/Multi-factor_authentication
Did you start from the top of the flowchart?
Ah, that. I have never used the 2 factor auth on my account. Checked it, and it's still deactivated.
Yes.
The last commit adds a checkbox in the advanced tab, "Use alternative login method", which might help.
The ticket for 2fa issues is #385
I activate it, generate an application password and get the error message "Failed getting PPFT value".
the first thing on the flowchart if you have the newest version is to log into skype for web with incognito mode (chrome), which I did, then it connected fine. @Memisn did that not work for you?
I got a similar error and login at my browser helped be able to login again.
It seems "Failed getting magic T value" happens when some additional step is required during the log in process. Today after failing to log in via this plugin I got this question when logging in via a web browser:
Is your security info still accurate? We just want to make sure this security info is up-to-date, so we can use it to verify your identity or alert you if there's ever a problem with your account. (my e-mail addresses were here)
After I answered this question, I could log in via the plugin.
I have this issue on a public server (Spectrum jabber transport). As I don't own the server I can't login to web.skype.com from that machine, however on my own device I didn't hit anything on web.skype.com (TOS,...). I have already disabled 2 factor auth.
@mtlive can you ask the operator of the public server to grab the latest version from git, so that you can use the "alternative auth" setting?
Thank you @EionRobb I will tell them. This is their GitHub: https://github.com/decent-im/decent.im .
Update: I figured it out how to fix it. I just headed to https://account.live.com/activity and marked the unusual activity (which was by the transport server) as "This was me". But I saw 'Incorrect password entered' logs at that page after doing so, which I rectified it by removing and registering again on the transport. I think it would be useful to include the recent activity page in the troubleshooting flowchart.
As another hint for someone hitting the problem. In my case web.skype.com suddenly wanted to send me a code for confirmation. So, if you hit the problem try to login to web.skype.com with your browser and the Skype account you are using. If it is a "real" Skype account and you choose to email the code they will automatically attach this email address as the Microsoft account name. Which somewhat counterfeits the confirmation requirement, doesn't it? They want me to confirm something and I can choose the target of the SMS or email freely? Rather smells like they wanted to promote the Skype account to a "real" Microsoft account. Anyway, as others said, if you hit the problem, there's something "in the way" on the Skype web interface and you should check there. Maybe some hint on the warning like "Try logging in to this account with your browser at https://web.skype.com." might be helpful, in addition to the "magic T" error statement ;-)
