Users see the unverified app warning on Google sign-in
The unverified app screen appears before the Google consent screenShort answer
Google shows the unverified app screen when an app requests sensitive or restricted scopes without approved verification. Fix it by requesting only the scopes you need, or by submitting the app for verification. Until then, the app is capped at 100 new users.
Fix it fast
1Find out which cause you have
List the scopes your code requests and compare them with the scopes on the consent screen in the Google Cloud console. The warning follows from sensitive or restricted scopes, or from a mismatch between the two.
grep -rn "googleapis.com/auth" src/ grep -rn "scope" src/main/resources/2Match what you see, then jump to its fix
- 1
The warning appears for every user outside the project, and sign-in works only after clicking throughThe app requests sensitive or restricted scopes and is not verifiedFix - 2
Only the developer's own account gets in; others are blocked or warnedThe app is in Testing status and the user is not a test userFix - 3
New users are refused after many people have already signed inYou hit the 100 new user capFix
- 1
What does the error look like?
The unverified app screen appears before the Google consent screenSign-in is blocked for accounts that are not on the test user list
Cause 1 of 3
The app requests sensitive or restricted scopes and is not verified
1Check
Google defines an unverified app as one that requests a sensitive or restricted scope. Find which of your scopes are in that class on the consent screen settings.
grep -rn "googleapis.com/auth" src/2Fix
Drop scopes you do not need. For the rest, start verification: add a privacy policy URL on the consent screen, verify your website in Search Console with an account that owns the project, then submit the app.
# Google Cloud console > APIs & Services > OAuth consent screen: add the privacy policy URL, then Submit for verification3Verify
Once approved, sign in with a fresh Google account that is not on any test list.
# open the sign-in link in a private window and confirm no warning appearsConfirmed by support.google.com
Cause 2 of 3
The app is in Testing status and the user is not a test user
1Check
In Testing status only the test users listed on the consent screen can authorize, up to 100 of them. Their authorizations, and any refresh token, expire seven days after consent unless the app asks only for email, profile and openid.
# Google Cloud console > OAuth consent screen settings: check the publishing status and the test user list2Fix
Add the people who need access as test users while you develop. To open the app to anyone with a Google Account, publish it to production; scopes that are sensitive or restricted then need verification.
# Consent screen settings: add test users (Testing) or use the Publish app button (production)3Verify
Sign in with a listed test user, and later with a normal account after publishing.
# repeat the sign-in flow in a private windowConfirmed by support.google.com
Cause 3 of 3
You hit the 100 new user cap
1Check
Unverified apps that request unapproved sensitive or restricted scopes are capped at 100 new users over the project's whole life. The cap cannot be reset.
# Google Cloud console > OAuth consent screen settings: look at the project's user count and status2Fix
Request verification; an appeal against the cap goes through verification.
# Submit the app for verification from the consent screen3Verify
After approval, new users can sign in without the cap applying.
# test with a new accountConfirmed by support.google.com
How do I stop it coming back?
- Ask only for the scopes the feature uses; email, profile and openid avoid most of this.
- Add the privacy policy and verify the domain before you launch publicly.
- Re-check verification when you add a redirect URL, change the product name or add scopes.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Related fixes
Security
Google sign-in stops with Error 400: redirect_uri_mismatch
redirect_uri_mismatch
Google compares the redirect_uri in your request with the authorized redirect URIs of that OAuth client, character by character.
3 causes, each with a fixSecurity
Jwts.parserBuilder() no longer compiles after upgrading JJWT
setSigningKey / parseClaimsJws / getBody shown as deprecated
JJWT 0.12.0 removed Jwts.parserBuilder() because Jwts.parser() now returns the builder itself.
3 causes, each with a fixSecurity
JJWT rejects a token because the signature does not match
Login works but every request with the issued token is rejected
JJWT recomputes the signature with the key you give the parser.
3 causes, each with a fixSecurity
Spring Boot cannot find a ClientRegistrationRepository bean for OAuth2 login
APPLICATION FAILED TO START
Boot creates the ClientRegistrationRepository from spring.security.oauth2.client.registration properties.
3 causes, each with a fixSecurity
Spring Security fails to resolve the issuer configuration for a JWT or Keycloak
The identity server is up but the Spring app fails on the first token
Spring Security fetches the issuer's discovery document before it can validate tokens.
3 causes, each with a fixSecurity
Spring Security cannot verify the CSRF token because the session is gone
InvalidCsrfTokenException
By default Spring Security keeps the expected CSRF token in the HTTP session.
3 causes, each with a fix