Bug 327205

Summary:	Google Accounts with Two-Step Verification will not log in
Product:	[Applications] kmail2	Reporter:	Jeb Eldridge <jebeld17>
Component:	config dialog	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
URL:	http://www.google.com/landing/2step/
Latest Commit:		Version Fixed In:

Description Jeb Eldridge 2013-11-06 05:37:27 UTC

If I have my Google account set up on a two-step verification system, which is much much safer than having just one password alone, I cannot log in using ANY KDE apps whatsoever. I've tried everything KDE, from KMail to Telepathy. And all I get is error messages, unfortunately :/

Two-step verification is an important leap in keeping user privacy at bay and keeping hackers out of our accounts, it is a shame that KDE still doesn't support it by default when other Linux GUIs do, such as GNOME 3.x and Unity with their own account management programs.

Please fix :)

Reproducible: Always

Steps to Reproduce:
1. Open KMail for the first time.
2. Attempt login to a Google account that has a two-step verification passcode.
3. System attempts login, fails every time.
Actual Results:  
Essentially, I cannot now synchronize my contacts, emails, Google Hangouts, or calendar notifications from my Google account on KDE.

Expected Results:  
After entering a password, a window should pop up explaining to sign in manually to allow KDE access to my Google account, just like what GNOME and Unity already offer.

Comment 1 Denis Kurz 2016-09-24 18:19:24 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 2 Denis Kurz 2017-01-07 21:42:52 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.