Use our own UI for GOA accounts

Bug #1813486 reported by Michael Terry on 2019-01-27
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Déjà Dup

Bug Description

GNOME might soon lose its Google API keys. And the ensuing discussion has made it clear that I should not rely on GOA alone for account sign ons.

I need to add UI to log into GNOME Drive for when GOA loses support.

GNOME issue about losing the keys:

Michael Terry (mterry) on 2019-01-27
Changed in deja-dup:
importance: Undecided → Critical
status: New → Triaged
Michael Terry (mterry) on 2019-01-27
description: updated
Michael Terry (mterry) wrote :

OK, a couple problems with supporting Google Drive if GNOME loses their key:
- No clear way to include our own key. Putting the secret in our source code is rightfully disapproved of by Google. Not clear how GNOME is getting away with it without anyone abusing it.
- No suitable duplicity backend to use. 'gio' only supports GOA's keys. 'gdocs' is EOL and can't work. 'pydrive' is not packaged in Fedora or Ubuntu.

So... I dunno. Seems like the best option is to just prepare a dialog explaining why users can't access their Drive with deja-dup anymore. And what to do about it.

I guess the next default backend would be Nextcloud.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers