Chrome's incognito disables Google Sign in button

Viewed 2756

So we have a sign up page in our app and it has Google sign in button. We have hooked it up using OAuth 2.0 and works absolutely fine when browsed in normal or incognito mode on all the the browsers but somehow gets disabled in Chrome's Incognito Mode. So on digging further we came across a post on Google's Blog site where they have explicitly mentioned this "we want to strengthen the Incognito protections in the meantime. In addition to deleting cookies every time you close the browser window in Incognito, we will also start blocking third-party cookies by default within each Incognito session" ( https://blog.google/products/chrome/more-intuitive-privacy-and-security-controls-chrome/ ). This feature was added in Chrome's version 83. Now the third party cookie disabling causes that issue and if we go to settings and select Allow all cookies then the button starts responding.

Now my question to the community is how come sites like Reddit or Pramp have their Google sign in button functioning in Chrome's Incognito even when we have Third-party cookies disabled in every Incognito session by default. Can we too have that same feature in our app? Is there any work around regarding this as the work around suggested earlier seems unfit to us.

0 Answers
Related