I am pulling data from a spreadsheet via Google Sheets V4 REST API and Ruby:
https://sheets.googleapis.com/v4/spreadsheets/MASTER_SPREADSHEET_ID/values/A:GH?key=GOOGLE_SERVER_KEY
I had this working before, until the spreadsheet was removed and recreated. Now I am getting a 403 error with the new spreadsheet.
APIs:
The Docs state that you can just append the url with an API Key, am I interpreting this wrong?
I faced the same problem and solved it.
The problem was the public scope of the Google sheet you were trying to access.
Enter the spreadsheets you want to access.
Click the Share button.
Click View Link.
If you set the public view of the spreadsheets you want to access to the link view, all users who want to access the link will be able to access it.
First, make sure you have a permission to call this spreadsheet. You can also try to change the status of this spreadsheet to public and checked if you can access it now. This 403 error is usually caused by incorrect or missed some configuration in Authorizing Requests. For more information, if you authorizing requests with OAuth 2.0, make sure you use proper scope with it.
Following up on what KENdi said, you will also get a
The remote server returned an error: (403) Forbidden.
If the API for the service you need is not enabled.
Related
I am trying to add the google one tap login to our internal website but I am getting the following warning. Although I have already added the main domain and sub domain(just to test) in Authorized redirect URIs and Authorized JavaScript origins but still getting this error.
I read in the document where it says no verification is required when the app is used internally.
Thanks in advance for any guidance
In order to add the new "Sign in with Google" option on the websites which are hosted on the dynamically created subdomains, one can use the solution provided by google is its integration via iframe.
The annoying part is that the documentation didn't mentioned this solution as another possible solution in its subdomain section.
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?
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.
So I'm trying to integrate Google login with Parse using the "Bring your own login" system. I was able to get the basic authorization functionality to work using the code snippets at https://groups.google.com/forum/#!topic/parse-developers/UUvTreGYOrI.
Now, to do some testing, I went ahead and manually deleted the user object via the Parse dashboard. However, I am now getting the following error when trying to access go through the signup workflow:
com.parse.ParseRequest$ParseRequestException: {"code":101,"message":"object not found for get"}
I tried clearing the cache and uninstalling the app, but the issue persists. Can anyone help me how to get around this and start the registration process afresh?
On a more fundamental note, this is my first time implementing code OAuth, logins, and ACLs. As such, any resource/tutorial that can give me code examples of this integration with Parse on both the CloudCode and the client (app) side would be highly appreciated (I believe the current official Parse tutorial uses Git and only has samples of the server side CloudCode).
Nevermind - I figured it out.
I had to delete the entry in the TokenStorage class on the Parse dashboard. I guess that's storing the token that links the login with the User object.
Anyway - I'm keeping this open to see if someone can point me to a good sample code for this workflow.
I am trying to use Google places api to search the location. But Unfortunately I am getting only 1 message in responce is REQUEST DENIED. I have created new API key, but the API ACCESS Menu shows some warning icons as shown in below image does it created any issues or any other issues belonging to API key ?
Please let me know how to overcome this issue.... thanks in advance!`
my request string is this
You should also never post your API Key on the Internet like in your request string above to prevent your key from being abused. Your API Key should be kept private like a password as any usage of your key will be logged against your account.
The request above works fine using my API Key, I would suggest generating another API Key on the API Access page of the APIs console. Also make sure that you have enabled the Places API under services, instructions are here.
The notification icons are there to notify you that you have not enabled billing on your account yet.
i have the same error. the error was resolved by append &sensor=false at the end of API
I've had this issue, turns out using the key for Android applications (the one used for the maps API) is wrong. I needed to create a key for browser applications. Once I used the browser key instead of the Android key everything worked fine.