| 1 |
On Monday 18 Aug 2014 11:38:58 Rich Freeman wrote: |
| 2 |
> On Mon, Aug 18, 2014 at 6:04 AM, Mick <michaelkintzios@×××××.com> wrote: |
| 3 |
|
| 4 |
> > A few months ago Google were using DAV for this purpose, but they decided |
| 5 |
> > to change their API. As a result older =< 4.4.11.1-r2 KDEPIM versions |
| 6 |
> > broke and one had to move to the current versions of KDEPIM in order to |
| 7 |
> > use Google Calendar integration. |
| 8 |
> |
| 9 |
> My problem with KDE and Google is that it seems like it doesn't work |
| 10 |
> with application-specific passwords - or at least it didn't use to |
| 11 |
> work with them. As a result I have to use two-factor login every time |
| 12 |
> I log into KDE, which is painful enough that I usually just close the |
| 13 |
> window and have stale data as a result. |
| 14 |
> |
| 15 |
> Perhaps this has been fixed. |
| 16 |
|
| 17 |
I understand that Google offers two factor authentication |
| 18 |
(https://www.google.com/landing/2step/#tab=how-it-works) for its services, but |
| 19 |
if you have not signed up for it you only need a single google account passwd |
| 20 |
to login. KDEWallet/Akonadi saves this when you create the google calendar |
| 21 |
resource and doesn't ask for it again. Of course, KDEWallet will ask for the |
| 22 |
master passwd, but depending on how you have configured it this would only |
| 23 |
happen once per login session. |
| 24 |
|
| 25 |
-- |
| 26 |
Regards, |
| 27 |
Mick |
Archives