Google OAuth 401 Error

TODO: collapasable, copyable, download, etc

I'm using NextAuth NodeJS code to do OAuth with Google. I created the google client app. I am able to sign in, but another developer on my team gets the following error: Acess blocked: authorisation error The OAuth client was not found. If youa re a develoepr of this app, see error details. Error 401: invalid_client.The error message "Access blocked: authorization error. The OAuth client was not found. Error 401: invalid_client" that your team member is encountering typically indicates an issue with the OAuth client configuration for your Google application. Here are some steps to troubleshoot and resolve this issue:

1. Check the Client ID and Client Secret: Ensure that the Client ID and Client Secret used in your NextAuth configuration match exactly with those provided by the Google Developer Console. Even a small typo can cause this error.

2. Verify Google Cloud Console Configuration:

   • Go to the Google Cloud Console.
   • Select your project.
   • Navigate to "APIs & Services" > "Credentials".
   • Confirm that the OAuth 2.0 client IDs are correctly set up.

3. Authorized Redirect URIs:

   • In the same section where you found your client IDs, check the "Authorized redirect URIs".
   • Ensure that the redirect URI in your NextAuth configuration matches exactly with one of the URIs listed in the Google Cloud Console.

4. Consent Screen Configuration:

   • Still in the Google Cloud Console, navigate to the "OAuth consent screen" tab.
   • Ensure that your application's consent screen is configured correctly and is in the correct publishing status (e.g., testing or production).

5. Usage of Client ID and Secret:

   • Double-check how the Client ID and Secret are being used in your code. If you're using environment variables, ensure they are correctly set in the environment where your colleague is running the application.

6. Access and Refresh Tokens:

   • If your application stores and reuses tokens, ensure that these tokens are valid and have not expired. Invalid or expired tokens can sometimes cause this error.

7. Google Developer Console Project:

   • Ensure that your colleague is added as a member or has access to the Google Cloud project if it's required.

8. Different Environments:

   • If you and your colleague are working in different environments (development, staging, production), ensure that the Google OAuth client is configured correctly for each environment.

9. Check for Service Disruptions:

   • Occasionally, this error can be caused by temporary issues on Google's end. Check Google's status page for any ongoing issues.

10. Logging and Detailed Error Messages:

    • Implement detailed logging in your authentication flow to capture more information about the error.

If you've gone through these steps and the issue persists, it could be helpful to share the relevant parts of your NextAuth configuration (without sensitive data like secrets), as this might provide more insights into the problem.

Google OAuth 401 Error created at Tue Jan 20 1970 16:17:41 GMT+0000 (Coordinated Universal Time)