https://bugs.kde.org/show_bug.cgi?id=434508
Tomas Trnka <tomastr...@gmx.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tomastr...@gmx.com
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #1 from Tomas Trnka <tomastr...@gmx.com> ---
I just stumbled upon this same issue. I guess it might be related to Google's
ongoing crackdown against using embedded webviews for authentication:
https://security.googleblog.com/2019/04/better-protection-against-man-in-middle.html
https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html
The official recommended way to handle authentication is to open a full-blown
browser so that people can reuse signed-in accounts and stored passwords. I
suppose KGAPI will need to be adjusted to launch a browser. Until that happens,
you can do it manually as a workaround:
Steps:
1.-4. See above.
5. A window opens asking you to sign in to Google. Select and copy the full URL
in the address bar of this window. Leave the window open but do not interact
with it further.
6. Open a new tab in your favourite browser. Paste the URL copied in Step 5 to
the address bar and navigate to it.
7. A page opens asking you to sign in to Google. Sign in and confirm granting
necessary permissions to Akonadi.
8. Your main browser should now be redirected to a blank page at
127.0.0.1:some_random_port_number. This passes the authentication tokens to
Akonadi behind the scenes. The Akonadi sign-in window opened in Step 5 should
now automatically disappear. Once that happens, you can close this blank tab in
your main browser.
--
You are receiving this mail because:
You are watching all bug changes.
