laravel socialite 3.0 getting error during Google+ login - laravel

laravel
Client error: GET https://www.googleapis.com/plus/v1/people/me?prettyPrint=false resulted in a 403 Forbidden response:
{"error":{"errors":[{"domain":"usageLimits","reason":"accessNotConfigured","message":"Project
892227784590 is not found (truncated...)

Make sure you've created an application in Google's console and also have your client id and client secret from google. Also make sure you've configured google option in your config/services.php.

Related

Q: Google OAuth 2 Error 400: redirect_uri_mismatch but redirect uri is compliant and already registered in Google Cloud Console

I am developing a NextJS application using next-auth with Google Oauth 2 as its authentication provider. The production build is running on Heroku. When attempting to sign in on my production build, Google OAuth is giving me "Error 400: redirect_uri_mismatch". Normally this would be an easy fix, except the exact uri is already registered in Cloud Console.
.
I have also tried added many different permutations of my uri, but this did not help.
This issue not solved by 11485271 or 69151061.
Error in question:
Error 400: redirect_uri_mismatch
You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy.
If you're the app developer, register the redirect URI in the Google Cloud Console.
Request Details
If you’re the app developer, make sure that these request details comply with Google policies.
redirect_uri: https://middcourses2.herokuapp.com/api/auth/callback/google
And here is a link to the list of authorized domains in GCP.
Solved! So for some reason, Google changed my Client ID and Client Secret after I already set up those env variables. Once I noticed the change and inputted the new values it worked fine.
For me, clientID was not the issue, but this was due to a trailing slash( / ).
redirect_uri must be an EXACT MATCH on the developers console.
In the Google Cloud console, I had http://localhost:8080 under the redirect URIs in the list while my code was sending http://localhost:8080/ while making the oAuth call.

Laravel Socialite Providers - Microsoft Issue

When implementing Laravel Socialite Providers for Microsoft to authenticate users below issue throws. How to fix this.
GuzzleHttp\Exception\ClientException
Client error: POST https://login.microsoftonline.com/common/oauth2/v2.0/token resulted in a 400 Bad Request response: {"error":"invalid_grant","error_description":"AADSTS70000: The request was denied because one or more scopes requested a (truncated...)
Azure Active Directory Permissions

Laravel Socialite Twitter Provider - Could not authenticate

I'm using Laravel Socialite in a project and added the Twitter Provider in order to be able to allow my users to integrate with their Twitter account. I followed the steps here https://socialiteproviders.com/Twitter/ and I'm getting the following error:
Received HTTP status code [401] with message "{"errors":[{"code":32,"message":"Could not authenticate you."}]}" when getting temporary credentials.
If I leave the TWITTER_REDIRECT_URI in my env file blank, the error goes away and the Oauth flow works exactly as it's supposed to. Is anyone else having this issue? If the TWITTER_REDIRECT_URI isn't needed why have it in the docs?

Bad Request when using Socialite on Facebook

I am using Socialite Package (https://laravel.com/docs/6.x/socialite) in my project.I have done following:
Register Application on Facebook
Get Client Secret and ID
Installed Socialite Package using composer
configure .env files
configure callback url
But when after successful callback, my app shows following errors on this command
Socialite::drive("facebook")->user()
error: Client error:
POST
https://graph.facebook.com/v3.3/oauth/access_tokenresulted in a400 Bad Request
Response:
{
"error":{
"message": "URL \u0644\u0648\u0688 \u0646\u06c1\u06cc\u06ba
\u06a9\u06cc\u0627 \u062c\u0627 \u0633\u06a9\u062a\ (truncated...)
A:\xampp\htdocs\PLAGX_FRONTEND\px-web\vendor\guzzlehttp\guzzle\src\Exception\RequestException.php
The issue is with the SSL of your callback url, the response seems to be not properly decoded by the receiver party. Turning SSL on your localhost or deployment server could help.

laravel authantication error with google API

I have been using Socilte Package for users login, I am using Facebook and Google.
Facebook is working fine but Google API is not working,
Showing an error while returning from Google.
403 - Forbidden
The Web server is configured to not list the contents of this directory or you do not have enough permissions to access the resource
Error is similar to this post
But I didn't found solution in this post. Google+ API is also enabled and no issue with credentials.
Domain is verified.

Resources