I have a google application. Right now all my auth in nodejs working well. But when I'm trying to login using google I have an error that "Sign in with Google temporarily disabled for this app"
I've tried to find where I can enable auth, but no solution.
I think that it is a problem with google console settings.
How should it work? - I need to log in with my google account
Have you checked if the google+ API is enabled?
Related
I use only google sign-in in my application, how do I add App access instructions for google to test my application. I am failing to find a way of instructing google on how to log in. I thought of using my own email address but then that will require me to authorize them when they try to log in.
You do not need to provide credentials, Just write in the instructions that your app are using Google Sign-in and it will work.
I have a Google Cloud App Engine app that functions correctly when either I allow unauthenticated AllUsers access or turn on IAM for controlling access in Identity Aware Proxy. However when I follow the instructions on this page https://cloud.google.com/iap/docs/cloud-run-sign-in to enable Cloud Run Hosted sign-in with external identities and attempt to access either the login page or the Google Cloud Run hosted sign-in page, I receive the following error in the browser.
"Could not fetch URI /computeMetadata/v1/instance/service-accounts/default/token?scopes=https://www.googleapis.com/auth/cloud-platform,https://www.googleapis.com/auth/identitytoolkit"
For context, the Google Cloud Run service hosting the user sign-in is set to allow all Unauthenticated. It should re-direct to the Google App Engine web app. I think this is related to permissions or redirects, but I am at a loss as to how to fix. Any thoughts? Thanks!
I attempted to fix by re-deploying the Cloud Run Service, switching IAP on and off, switching between IAM and external identities, but to no success.
Thanks #John Hanley, I discovered that one my compute engine service account was disabled for some reason within the project. Re-enabling solved the problem partially. I'll spend more time matrix out the permissions and re-directs to make sure they are aligned.
I originally thought I completely answered my own question and solved my problem. Unfortunately, I only solved one of the problems with my implementation of the external identities authentication method.
Description of the other problem:
I enabled email/password and Google as providers, but when I click on the the option to authenticate with Google, I receive the following text in the browser: "The requested action is invalid."
At the Console in Dev Tools I get the following error:
GET https://www.googleapis.com/identitytoolkit/v3/relyingparty/getProjectConfig?key=*mykey*&cb=1599165379363 403
The following url is displayed in the URL bar:
https://.firebaseapp.com/__/auth/handler?apiKey=mykey&appName=%5BDEFAULT%5D-firebaseui-temp&authType=signInViaRedirect&providerId=google.com&customParameters=%7B%22hl%22%3A%22en%22%7D&scopes=profile&redirectUrl=https%3A%2F%2Fiap-gcip-hosted-ui-app-engine-app-myserver-uc.a.run.app%2F%3FapiKey%3Dmykey**&v=7.16.0&fw=FirebaseUI-web
mykey and myserver were removed for this post and is not the actual values.
Email/password sign-in works, but not the Google sign-in. What am I missing here?
When attempting to log in with Google OAuth via the TikTok in-app browser it says "Authorization Error Error 403 disallowed_useragent Google can't sign you in safely inside this app. You can use Google sign-in by visiting this app's website in a browser like Safari or Chrome."
Thinking this is either a call by Google to prevent login within TikTok or they simply haven't added this user agent yet.
Google OAuth does not work in embedded web views per policy. See https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html.
You should reach out to the app developer to recommend they use one of the alternatives recommended like Chrome Custom Tabs.
I was trying to add the google login to my laravel project. but it gives a Client error. Given below is the error i got. I successfully installed the socialite as well.
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 983930379932 is not found (truncated...)
Go to https://console.cloud.google.com/apis and enable Google+ api.
Took me 3 hours to find out that Google Cloud does not automatically enable the api for you when you create OAuth service.
Remember you have to register your google app within googles service as well. That error if I remember correctly is simply telling you that you aren't allowed to use google services.
I am not super sure if this steps are up to date, but it shouldn't be that different: https://itsolutionstuff.com/post/laravel-5-google-oauth-authentication-using-socialite-packageexample.html
First Open your Google Console Account from Here : console.developers.google.com
Select your project.
After this you have to click on google+ API detail page.
Now we can enable API.
I have wp7 app that should consume Google Latitude API. It requires my app to be authenticated with OAuth 2.0 access token. To archive that I'm using authentication flow for native applications (described here http://code.google.com/apis/accounts/docs/OAuth2.html#IA). When my app navigates to Request for Permissions page from within browser control and I'm clicking on "Allow access", the server respond to me with "Deniend error=acces_denied" page.
Google Latitude API is enabled on my apis console btw. Can anybody help me to determine where is the problem?
[EDIT]
Thanks to #gyurisc i figured out that it works on desktop browser, I have my access token. But there is still a mystery whats wrong with browser control of WP7! Why it returns "Access Denied" error if I allow access.
[EDIT]
I've posted an issue in Google Latitude Issue Tracker OAuth 2.0 dialog doesnt work properly on WP7
The temporary workaround from google team is to replace "account.google.com" to "sandbox.google.com". They will try to fix this bug asap on production server