Commit 6d7456fd authored by Elvis Angelaccio's avatar Elvis Angelaccio
Browse files

Update Google Drive credentials for qtkeychain backend

These credentials were created back in Akademy 2019 but were never
shipped because Google never verified the "OAuth consent screen" shown
to the users. (I never understood if Google didn't like something or if
simply no one at Google looked at it).

However, these credentials do work if you go in the "advanced" section
of the oauth screen and click on the "I trust KDE e.V. as developer"
button. So I think is better to ship them anyway, rather than ship the
old credentials that have been broken for years.

The qtkeychain backend is disabled by default anyway and is only a fallback
for those who don't want to use the main KAccounts backend, which is the
recommended one.

CCBUG: 439639
CCMAIL: kde-ev-board@kde.org
parent 4a3c31ef
Pipeline #257832 passed with stage
in 3 minutes and 1 second
......@@ -21,8 +21,8 @@
#include <KIO/Job> //for stat.h
#include <KGAPI/AuthJob>
QString KeychainAccountManager::s_apiKey = QStringLiteral("554041944266.apps.googleusercontent.com");
QString KeychainAccountManager::s_apiSecret = QStringLiteral("mdT1DjzohxN3npUUzkENT0gO");
QString KeychainAccountManager::s_apiKey = QStringLiteral("836279663462-qq9rt1k4smgqhvt461r6l54vo9qm09bg.apps.googleusercontent.com");
QString KeychainAccountManager::s_apiSecret = QStringLiteral("5-k19mrwsAud5a1r-qijtTJQ");
QSet<QString> KeychainAccountManager::accounts()
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment