I recently updated my Google Calendar Events script to use the newest GIS authentication method required for newly created apps on Google Dev Console and it was working great. I built the test form sometime late last year.
Just went back in to test it and it was not working, throwing an error about Cross Origin when trying to authenticate.
I asked ChatGPT why I was getting this error now and it said
When CORP* is present, Chrome automatically applies popup isolation rules that can break Google OAuth popups in certain contexts (iframes, redirects, or strict sites). This is a Chrome behavior change, not your code. 👉 Result: Google Identity popup can’t communicate back → authorization fails. Why it worked before Chrome recently tightened enforcement around: • CORP • popups • embedded contexts Older Chrome versions were more permissive. No code changes required for this to start failing.
*CORP is short for Cross-Origin-Resource-Policy and this is in the headers of Laserfiche Forms on LF Cloud.
Assuming Google really did make this change very recently and break the authentication to their own API for scripts that use the pop up method of authentication (the most convenient method), I switched to using the redirect method where it continued to fail to authenticate.
ChatGPT had this to say about my redirect URL
That page is not a true top-level navigation target app.laserfiche.com/forms/... is a hosted application shell, not a standalone page. OAuth redirect requires: Full page navigation Top-level window Ability to receive and parse ?code=... Laserfiche Forms does not expose a place for you to run OAuth callback logic. So Google redirects → Laserfiche → Laserfiche swallows the code → page reloads. That’s exactly what you’re seeing.
🧠What this means (important) You CANNOT complete Google OAuth directly inside a Laserfiche Form. Not with: Popup Redirect GIS Legacy gapi Any workaround This is a platform limitation, not your code.
This leaves me in an impossible situation. I am not sure what to believe here. This would mean Google (and Microsoft for that matter because Edge is doing the same thing) just implemented a change that breaks the ability for any Laserfiche users to use the new GIS Auth method and there is no option to create accounts that work with the old auth method anymore, only my original accounts created in 2016 work now.