I have recently been unable to authenticate using Google SAML with the RingCentral desktop app or Classic app. I do not believe the issue to be a SAML issue as the account being used to authenticate will work in other cases with RingCentral like RingCentral Phone, RC app on IOS & Android.
After some searching I found this blog from Google.
https://developers.googleblog.com/2020/08/guidance-for-our-effort-to-block-less-secure-browser-and-apps.html
Which explains the behavior I am experiencing with the RingCentral desktop apps previously mentioned. I believe both the RC app/classic are running an embedded version of Electron and would fall in the embedded browser category. I think this may be a wider issue at least in my instance and hasn't been a real problem yet due to SAML being able to have a persistent session, but after log out I have not been able to authenticate again.
Actual text of the message from Google.
This browser or app may not be secure. Learn more
Try using a different browser. If you’re already using a supported browser, you can refresh your screen and try again to sign in.
My question would be has there been any further reporting of this issue or am I an isolated case?
