Re: PP 5.6 and Google's new OATH2 Changes
Posted: Wed Apr 23, 2025 8:37 pm
I haven't seen that message in the account I'm using for testing purposes; and 2SV is not enabled. But the account is tied to my phone -- which I thought could possibly be a reason -- so I accessed the dev console with another account that has virtually nothing attached to it, and still don't see it.
Where do you see that message at? (not that I don't believe you, the article is clear on the May 12/13 date; I just want to know why I haven't seen it).
That being said, some ideas:
- Only enable 2FA when you need to access the console (ie. to add new accounts); then disable it again
- For the purpose of the necessary Client Id/Secret -- Use an account that you don't need to access manually (or create a new account for the purpose), and enable 2FA on that account. I would suggest that you use PP to checkmail this account to keep it active (and to possibly receive messages from Google regarding it, although you could specify a different email address for Google to send you notifications in the Dev console)
Where do you see that message at? (not that I don't believe you, the article is clear on the May 12/13 date; I just want to know why I haven't seen it).
That being said, some ideas:
- Only enable 2FA when you need to access the console (ie. to add new accounts); then disable it again
- For the purpose of the necessary Client Id/Secret -- Use an account that you don't need to access manually (or create a new account for the purpose), and enable 2FA on that account. I would suggest that you use PP to checkmail this account to keep it active (and to possibly receive messages from Google regarding it, although you could specify a different email address for Google to send you notifications in the Dev console)