Request had insufficient authentication scope [500] - spring-mvc

I have simple user class doing a create and update in Datastore. It's running fine locally, but when I deploy it on Kubernetes, it provides me with the below response:
{
"timestamp": 1525833559351,
"status": 500,
"error": "Internal Server Error",
"exception": "com.google.cloud.datastore.DatastoreException",
"message": "Request had insufficient authentication scopes.",
"path": "/api/test/sample/5629499534213120"
}
For reference, I have followed this Stack Overflow link.

Related

Empty referrer in YouTube API requests

I'm trying to retrieve a channel's video list from the YouTube API. Actually, this functionality is already implemented, but suddenly stopped working.
Here's what I have:
A GET request to the search endpoint: https://www.googleapis.com/youtube/v3/search;
Some query params:
part=snippet,id
channelId=UCSJ4gkVC6NrvII8umztf0Ow (just an example)
maxResults=5
order=date
key=[MY_API_KEY]
I guess everything's alright, but for some reason I get this response:
{
"error": {
"code": 403,
"message": "Requests from referer <empty> are blocked.",
"errors": [
{
"message": "Requests from referer <empty> are blocked.",
"domain": "global",
"reason": "forbidden"
}
],
"status": "PERMISSION_DENIED"
}
}
I really don't know what's wrong, and every request returns the same error.
Can someone help me please?
Thanks for the attention!

Google analytics creating accoung, insufficientPermissions, your project does not have access to this feature

I'm trying to create an account via google api from symfony using the mediafigaro/google-analytics-api-symfony.
I got my token from jwt with the "**https://www.googleapis.com/auth/analytics.provision**" scope.
But when I send the post request, I got this exception:
{
"error": {
"errors": [
{
"domain": "global",
"reason": "insufficientPermissions",
"message": "Your project does not have access to this feature."
}
],
"code": 403,
"message": "Your project does not have access to this feature."
}
}
I already gave to my service account, the access to the main analytics account

Google Identity Toolkit failing to sign-up new user: Error code: Internal error encountered

New users trying to setup logins that aren't #google.com are hitting issues using Google Identity Toolkit. This has been working fine for a long time so not sure what's up. Looks like this:
In the console seeing a 500 error coming back when calling this URL:
https://www.googleapis.com/identitytoolkit/v3/relyingparty/setAccountInfo?key=<key>
POST data:
{"email":"nlckeweo#sharklasers.com","displayName":"test","password":"password"}
API response:
{
"error": {
"code": 500,
"message": "Internal error encountered.",
"errors": [
{
"message": "Internal error encountered.",
"domain": "global",
"reason": "backendError"
}
],
"status": "INTERNAL"
}
}

Adding ACL records for FreeBusyReader

I am trying to add a new ACL record to add a domain as freeBusyReader as described here.
Whenever I POST to
https://www.googleapis.com/calendar/v3/calendars/r...#resource.calendar.google.com/acl with a new domain I receive an error:
# Request
{
"scope": {
"type": "domain",
"value": "domain.com"
},
"role": "freeBusyReader"
}
# Reply
{
"error": {
"errors": [
{
"domain": "global",
"reason": "notFound",
"message": "Not Found"
}
],
"code": 404,
"message": "Not Found"
}
}
Weirdly though, it works for domains for which there is already some ACL rule. Those I can even change, so I assume that neither existence of the resource nor authorization is not the problem as suggested in the docs.
You can check this documentation about How to update the ACL of a Google Calendar with the Google APIs Explorer. If the user you want to grant access to is included in the response, you can proceed to update the ACL of the calendar.
For more info:
Working with ACl in Google Calendar

Google identity toolkit returns "Backend error"

Our application using google-identity-toolkit for authentication is receiving a 500 "backendError" from the verifyAssertion API. This occurs about 30% of the time and started happening about 1 week ago. 70% of the time the call succeeds. Our app has not changed in 6 months. Is there a broken server out there in the pool somewhere?
Error message:
{
"error": {
"errors": [
{
"domain": "global",
"reason": "backendError",
"message": "Backend Error"
}
],
"code": 500,
"message": "Backend Error"
}
}

Resources