Bug 339355

Summary: for each access to a google service we must have a distinct authorization
Product: [Applications] digikam Reporter: Philippe ROUBACH <philippe.roubach>
Component: Plugin-WebService-GoogleAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: caulier.gilles, dinhthanhtrung1996, metzpinguin
Priority: NOR    
Version: 6.0.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In: 7.2.0
Sentry Crash Report:

Description Philippe ROUBACH 2014-09-24 10:53:28 UTC 
for picasaweb export i must have a connection with its authorization
for google drive export i must have a connection with its authorization

Google unified the authorization access procedure . there is now one id and one password for all services .

digikam must unify the access to google services .





Reproducible: Always
Comment 1 Philippe ROUBACH 2014-09-24 10:53:58 UTC 
openssue 13.1 , kde 4.14.1
digikam 4.3.0
Comment 3 caulier.gilles 2015-05-19 10:13:01 UTC 
*** Bug 342150 has been marked as a duplicate of this bug. ***
Comment 4 caulier.gilles 2018-06-16 12:39:13 UTC 
Thanh,

This file still valid with your GSoC 2018 devel branch ?

Best

Gilles Caulier
Comment 5 caulier.gilles 2018-08-14 14:48:31 UTC 
Thanh,

This file still valid with O2 authentification ?

Gilles
Comment 6 Philippe ROUBACH 2019-02-28 12:24:18 UTC 
problem still there

we have 2 separate authorizations for Google drive and photo
Comment 7 caulier.gilles 2019-02-28 12:45:04 UTC 
...and 2 Google web-services not unified in Google infrastructures, as i know, so for me the behavior sound logic.

Gilles Caulier
Comment 8 Maik Qualmann 2019-02-28 12:52:12 UTC 
Yes, different web service APIs with different tokens. We can not merge it.

Maik
Comment 9 Philippe ROUBACH 2019-02-28 13:06:25 UTC 
yes you can

one procedure to connect to 2 google services.

one dialog for user to supply id and pwd and for the software 2 dialogs with google services
Comment 10 Maik Qualmann 2019-02-28 14:18:47 UTC 
No we can not.
1. We do not want to have Google access data and store them.
2. It is not possible to enter the access data in the external browser, also the App must be authorized by the user, this is only possible on the Google login page. I also think that this would contradict the Google App Guidelines and the App would be locked from Google.

Maik
Comment 11 Maik Qualmann 2021-02-07 12:09:43 UTC 
Since Google only allows login to its services with supported native browsers, this wish is no longer possible.

Maik