MMM-GooglePhotos ;Google OAuth Developer

[Rags]

Hello everyone,
I have been receiving alerts from Google;

“Hello Google OAuth Developer,
We’re writing to remind you that the OAuth out-of-band (OOB) flow will be deprecated on October 3, 2022, to protect your users from phishing and app impersonation attacks.
Please see the Making Google OAuth interactions safer by using more secure OAuth flows blog post to learn about the deprecation
Follow the Out-of-band (OOB) Migration Guide to migrate your app to an alternative method.”

So I am running the Google-Photos module to display my photos on the MM. I had followed the setup instructions as per the requirements of the module and the module is running without any hitch since the last two years. Would I have to make changes now to comply with the Google alerts? Please guide me.
Thanks

[sdetweil]

@Rags the module author, or someone will have to update the module code

[Rags]

@sdetweil Thanks, so can @aneaville, follow up please. The google photos modules is pretty neat and quite a conversation starter, and it would be a shame if it stops working.

[sdetweil]

@Rags open an issue on the modules GitHub page. not here.

[Rags]

@sdetweil Roger Sir.

[Rags]

@sdetweil Okay I see that the issue has already been opened in the modules page and under discussion. Hope it is resolved. Thanks

[sdetweil]

@Rags looks like someone has a workaround for sane issue

[MMRIZE]

Hmmmm… That module is still maintained? or abandoned? (This is a very stupid question for me. because myself threw it to @aneaville . If he is not maintaining this module anymore , I’ll retake it again.)

[sdetweil]

@MMRIZE it was last updated about this time last year…

[MMRIZE]

Ok. I tested the module by myself. Google changed some policies, so the guide of README.md in the module is somewhat outdated.

Here is a simple fixture;

1. Selection of Application type on Create OAuth client ID should be Desktop app not TVs and Limited input devices and others. (Step 7 of the guide)

2. When generating the token,
   
   the browser will open and then ask for some consent. (Despite of warning for test/unverified app, do it anyway. You can remove that warning by your app is published.). But after confirmation, the page might be directed to ERR_CONNECTION_REFUSED error page. Don’t panic and see the URL of that error page. It would be something like;

http ://localhost/?code=4/SOME_HASHED_CODE_OF_YOURS...&scope=https://www.googleapis.com/auth/photoslibrary.sharing…

Copy the marked portion of your browser, then paste it into your terminal.
(Step 10 of the guide)

Boom, it will work.

However, I think the module has become legacy and need updating with recent skill. I hope I have some time to upgrade it.