I can't sign in with a 403 error even though I have "no verification required" status with oauth.

[hamejirou]

I was using OAuth for Google Signin for a service in operation. Since the end of last year, I have suddenly been unable to sign in with a 403 error. The error message is "You have not completed Google's review process".

GCP's oauth authentication The status on the administration page is.
- "No verification required."
- Public status is "Production environment".
- No scope is used that requires validation.

What is the cause of the error?
How can I deal with it?

Thank you in advance.

[hamejirou]

As I have not received a reply on this matter, I have started the review process by changing the logo to try and get the app reviewed.
The review process was successful. However, I am still getting the same error.
What on earth is the problem?

Also, in the email notifying me that the review had passed, it stated that I should email us directly if I have any other questions, but there was no contact information for this.

If you can't answer my questions here, I would like to know where I can contact you.

[shaaland]

Is this what you are trying to do: 
https://developers.google.com/identity/sign-in/web/sign-in ? 

I suggest posting this question to the Google Developers community here, and this will be the right place to get support for App Authentication questions.  There are other tabs for Android apps and other situations that you may be in...hard to tell from your question as it's lacking these details.

If I'm misunderstanding and you are using one of our Google Cloud Products like Application Integration, Cloud Workflows, EventArc, Tasks, etc... let us know and we can try to get you more direct help! 

[hamejirou]

Thanks for the reply.

That is not what I am trying to do.
I am not trying to handle the login process using only js, but the following.

1. when a user presses the 'Login with Google' button, they are redirected to an endpoint that generates the URL for the oauth.
2. at that endpoint, redirect to the generated URL for oauth
3. the google oauth login screen is displayed.

As per your advice, I will ask the Developers community.

Thank you.

[hamejirou]

As recommended, we have submitted it to the developer community. I received a reply, but it said, "As we operate on a volunteer basis, only Google Staff can determine the details."

I thought it was correct to ask the question here in the community, as I am in the situation of setting up an oauth on the GCP console.

Also, what I am trying to do is not about android app authentication, but about google login on a web page. (normal browser browsing, not android native app webview).

I would like to know the appropriate place to have a Google Staff member check the status of my configuration in GCP and tell me what caused it and how to fix it.

[lawrencenelson · Accepted solution]

Hi @hamejirou,

The best way to resolve this issue is to contact Google Cloud Support. You can purchase a support package through Google Cloud Customer Care, which allows them to create a ticket directly with the OAuth team for further investigation of your application.

Thank you.