Google Photos API Credentials

[Maik Qualmann]

Do you already have your own app key? If not, you would need to submit the 
Google Import Tool to Google, have it evaluated, and approved. We, as 
developers, have concerns about this. An app key works a little differently 
than a key for the Maps API.

Maik

Am Freitag, 21. März 2025, 07:35:09 Mitteleuropäische Normalzeit schrieb 
Gilles Caulier:
> Hi,
> 
> yes the APi key is encrypted on the code to please Google to work.
> 
> If you want to try your own key just pass the key string directly here :
> 
> https://invent.kde.org/graphics/digikam/-/blob/master/core/dplugins/generic/
> webservices/google/gstalkerbase.cpp?ref_type=heads#L66
> 
> You have 2 strings to pass :
> 
> - the identity key
> - the shared key.
> 
> Replace the 2 calls with WSToolUtils::decodeKey(d->sharedKey) with
> QLatin1String("_my google_key_") as string not encrypted.
> 
> Best regards
> 
> Gilles Caulier
> 
> Le mar. 18 mars 2025 à 12:49, Wilson Bailey <wilsonrandallbailey at gmail.com>
> 
> a écrit :
> > What is the encoding of the QString Identity and QString sharedKey in
> > gstalkerbase.cpp?
> > 
> > I want to compile digiKam with my own credentials, but I'm not a C++
> > developer so I'm having a little trouble understanding how the Google
> > ClientID and Google Client Secret are encoded and decoded.
> > 
> > Any guidance would be appreciated.
> > 
> > -W