Fwd: [Action Required] Migrate your OAuth out-of-band flow to an alternative method before Oct. 3, 2022

[Neofytos Kolokotronis]

Hi people,

We received the following email from Google regarding the deprecation of
OAuth out-of-band (OOB) flow.

As we don't know which KDE app or library corresponds to the OAuth
client ID shared from them at the end of the email, we thought it is
possibly something relevant to the kde-pim team.

It's worth checking if it affects any kde-pim apps. If not, and you
happen to know which app they might be referring to, do reach out. 

Cheers,
Neofytos 

-------- Original Message -------- 

		SUBJECT:
 		[Action Required] Migrate your OAuth out-of-band flow to an
alternative method before Oct. 3, 2022

		DATE:
 		04.05.2022 06:28

		FROM:
 		Google Developers <GoogleDevelopers-noreply at google.com>

		TO:
 		kde-ev-board at kde.org

		REPLY-TO:
 		Google Developers <GoogleDevelopers-noreply at google.com>, "KDE e.V.
Board" <kde-ev-board at kde.org>

OAuth out-of-band flow will be blocked for your production OAuth
clients. 
_Our records indicate you have OAuth clients that used the OAuth OOB
flow in the past._ 

Hello Google OAuth Developer, 

We are writing to inform you that OAuth out-of-band (OOB) flow will be
deprecated on OCTOBER 3, 2022, to protect users from phishing and app
impersonation attacks. 

WHAT DO I NEED TO KNOW?

Starting OCTOBER 3, 2022, we will block OOB requests to Google's OAuth
2.0 authorization endpoint for existing clients. Apps using OOB in
testing [1] mode will not be affected. However, we strongly recommend
you to migrate them to safer methods as these apps will be immediately
blocked when switching to in production [2] status. 

NOTE: New OOB usage has already been disallowed since FEBRUARY 28, 2022.


BELOW ARE KEY DATES FOR COMPLIANCE 

 	* SEPTEMBER 5, 2022: A user-facing warning message may be displayed to
non-compliant OAuth requests
 	* OCTOBER 3, 2022: The OOB flow is blocked for all clients and users
will see the error page.

Please check out our recent blog post about Making Google OAuth
interactions safer [3] for more information. 

WHAT DO I NEED TO DO?

MIGRATE YOUR APP(S) TO AN APPROPRIATE ALTERNATIVE METHOD BY FOLLOWING
THESE INSTRUCTIONS: 

 	* Determine your app(s) client type [4] from your Google Cloud project
by following the client links below.
 	* Migrate your app(s) to a more secure alternative method by following
the instructions in the blog post above for your client type.

If necessary, you may request a one-time extension [5] for migrating
your app until JANUARY 31, 2023. KEEP IN MIND THAT ALL OOB AUTHORIZATION
REQUESTS WILL BE BLOCKED ON FEBRUARY 1, 2023. 

The following OAuth client(s) will be blocked on Oct 3, 2022. 

OAUTH CLIENT LIST: 

	* Project ID: api-project-554041944266 [6] 

 	* Client: 554041944266.apps.googleusercontent.com [7]

Thanks for choosing Google OAuth. 

— THE GOOGLE OAUTH DEVELOPER TEAM 

(c) 2022 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043 

You have received this mandatory service announcement to update you
about important changes to Google services you use. 

Links:
------
[1]
https://notifications.google.com/g/p/AD-FnEzXjPAodL841i0TMS9dVW8wAcV2DBSi7kgMhR7GMGt8vrFSInHGB5_YzVQgLbL1-6NJiBUPDMjSgMPTIThiksCq0_e0GjvrM2PPCsZRTXLnp3xFqpFr0MNO_GLZKLimKcdC7cMTCNYITnNJ5I--OYs9inS7faEE
[2]
https://notifications.google.com/g/p/AD-FnEwaHLKjw6uHY2kHklgNq-DkFVCvP7nVUY14wkVg6WU3DS6mYoG4AD2G8EG4J4BF8x3_iJR1Ry0czVexT6qwOPNo1wUKMT57-nLALNl08llGodpNQ1jBhlSgpv1uG3qM4rQEak8l6EbuqXSAq26PZmq38wUwSMK8swKb
[3]
https://notifications.google.com/g/p/AD-FnExGiMvEItiO95zTaCXO4Y7wYtav1svQwQm_YamednoumkbxcvO7GsmmB6IvNxt5AMNQxRD8TvMXviso8hEYXWTD2fack85n2In1d2zgD2-VcgZgvm0TPMFEIJnPAVnFNbeDrW5SYy16zdwE
[4]
https://notifications.google.com/g/p/AD-FnExCZvcaxRYqsOKINAOnPeLI0NDw21Txfn6PCO9G6qc65c6kuG1meQ8e2cMNwmZQixED08qi40ENli_9jwZmejXTGyY_gWl7cTEm5ASOu1PGEbw43H46kljkQLL-ggSr9531mJ0Yw-duZwRkFoGeeg_l1gKtoDGz3BuTzBr1n7DSt7wh
[5]
https://notifications.google.com/g/p/AD-FnEwcks7UknjLivCascIfgaSpZgzevMidjLakBw62Qv0jirhb31yGc_tuf3HRJ36xcTZ9pMjisWq9iPKrdz3xxOO-0LxV1U1l06T1orhbuHuIXrbeK5CQVqg9EujSjJL0Tct4A2eBrFCC-pb4lNuvRLrPhgSKGnWy35dVUxrL0QdA8LFyrPsUiQ
[6]
https://notifications.google.com/g/p/AD-FnEy5uAkRw7akaCs3E0AGUj4ydtHvAVs_qfS0RlvMLm91D9xJ-aW0yRKzwWw7-nxS2xjguYTQ1bZIapccT2w2FWUus740-GtGDrKIUpIIkrYJNGdu96ZKi4hAnSfdWRBAMHbE_Ge1wwX-Jdc
[7]
https://notifications.google.com/g/p/AD-FnEyUn2nIb4q6PinQrGZEtHbOIiBMyuhF4AFYcWVGd-cZIe4VFfVBnHsX7Vn1EYRnR00QQG2gxmW1drN6B50pJedJ45h_uAix0Avf5ch8EjP4N3bJoN_u0mGMPumawaQEotB4pis9pcTCDYHXy_KZbe9X-oZXrn2xlEA4ZJb9Jl9iQ2y3TeJvMMhC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20220518/dd2edd02/attachment.htm>