Different people have reported this using different languages but it can also be reproduced using the graph explorer.
This is a rather severe issue. Not only can I not use the v1.o endpoint, If I implement this against the beta endpoint I have no idea how long it will work. It puzzles me that I found other people reporting this (on the sdks instead of on the api) from over a year ago and is still not resolved. Perhaps not much used feature...
after creating a mail try to add a reference attachment. For the v1.0 endpoint this looks something like
using v1.0 endpoint
if you execute this you get: a bad request [400] Note that the sourceUrl property does not even exist on the v1.0 resources (see https://learn.microsoft.com/en-us/graph/api/resources/referenceattachment?view=graph-rest-1.0)
{
"error": {
"code": "ErrorInvalidProperty",
"message": "The property 'SourceUrl' is required when creating the entity.",
"innerError": {
"date": "2021-01-08T16:52:31",
"request-id": "2b8b4c2a-0f21-4691-bebc-574a30a9973a",
"client-request-id": "c42b7a0f-b6cb-0d7a-b461-d6ac026067a4"
}
}
}
Executing against the beta endpoint is possible, that one does contain the SourceUrl property, among others that are not in v1.0. (see https://learn.microsoft.com/zh-tw/graph/api/resources/referenceattachment?view=graph-rest-beta)
Try in graph explorer against beta endpoint
Related
I am trying to fetch data from Google Sheets via the Azure Data Factory. I have a data flow configured, and a Google Sheets Linked Service configured as well. The Google Sheets Linked Service is using an API key that has no Application Restrictions, and for API restrictions, it is restricted to Google Sheets. When I test the connection, it is successful. However, when I try to fetch a spreadsheet using the data flow in debug mode, I get the error:
at Source 'GoogleSheetsOutput': Failure to read most recent page request: DF-REST_001 - Error response from server: Some({
"error": {
"code": 403,
"message": "The caller does not have permission",
"status": "PERMISSION_DENIED"
}
}), Status code: 403. Please check your request url and body. (url:https://sheets.googleapis.com/v4/spreadsheets/<my_spreadsheet_id>/values/Sheet1!A2:B3,request body: None, request method: GET)
I made a service account, and shared the google sheet with the service account e-mail, and I also shared it with the admin on the account, which is where the API Key was made.
Any ideas what I need to do here? I would also prefer to use oauth / service account instead if possible, so I am happy to go down that route if there is some documentation I can follow.
"error": { "code": 403, "message": "The caller does not have permission", "status": "PERMISSION_DENIED" }
I tried to repro this and got the same error.
To solve this, I changed access of my google sheets from restricted to Anyone with the link
It worked and data is previewed without error.
We are exploring google Cloud Endpoints to expose gRPC services as REST APIs. These services use proto3 messages containing Any type fields.
Does Cloud Endpoints' Extensible Service Proxy (ESP) support JSON transcoding of Any fields embedding custom message types? Out of the box, it does not seem to support this and returns the following error
{
"code": 13,
"message": "Type 'type.acmeapis.com/acme.v1.Augmentation' cannot be found.",
"details": [
{
"#type": "type.googleapis.com/google.rpc.DebugInfo",
"stackEntries": [],
"detail": "internal"
}
]
}
Would this require a TypeRegistry configured on the ESP and if so is there a way to do this?
I've not tried using Cloud Endpoints with messages that include Any but I think it's unlikely that the proxy could be configured to transcode the enveloped message. It's possible but I think unlikely that even Envoy would enable this (but, again I don't know).
It's unclear what the semantics would be of the resulting REST API if this were to work:
rpc AddGeneric (AddGenericRequest) returns (AddGenericResponse) {}
Becomes, perhaps:
post: "v1alpha/add"
body: "generic"
Which using Any would be a type comprising an array of bytes and a string descriptor which is understandable as a REST API but, presumably the reason behind your question, requires the REST client to then decode the enveloped message.
But, if the transcoding were to recursively transcode enveloped messages, then this one (!) method would need to be defined with multiple possible message body types:
post: "v1alpha/add"
body: ["type-a" | "type-b" | "type-c" | ... ]
Which, while convenient seems a little un-RESTful. There's no requirement that transcoding produce RESTful APIs but it may explain the complexity involved.
To get a definitive response, I recommend you raise an issue on the Google-maintained GitHub repo for ESPv2. The folks there are responsive and helpful.
We had integrated our application with Microsoft Graph API enabling user to access their outlook through our application.
The integration works fine with office365 users but having intermittent issues with users in on-premise server.
Initially after enabling HMA in on-premise server the integration started working, but for past two weeks we are facing issue with the integration and receiving error message as below.
HTTP error: 404
Error code: MailboxNotEnabledForRESTAPI or MailboxNotSupportedForRESTAPI
Error message: "REST API is not yet supported for this mailbox."
But we had not made any recent changes to server or Graph API access.
Surprisingly, it started to working today as this was sporadic we need assistance in understanding the issue. Any help is greatly appreciated.
Update: We started seeing the error again early today and we have captured the following log information.
{
"error": {
"code": "ResourceNotFound",
"message": "Resource could not be discovered.",
"innerError": {
"date": "2020-10-30T08:03:20",
"request-id": "c1f461d7-0757-4a54-a727-58cb0da7fe5d",
"client-request-id": "c1f461d7-0757-4a54-a727-58cb0da7fe5d"
}
}
}
This post is not an answer :-(, but should provide more details because we are running into the same issue.
To isolate the problem, we only using postman. We are not able to create a "working token" with postman. We tried like every possible O-Auth flow :-). When we use the token generated by "Graph Playground" requests are working.
What means "working token":
Request to: https://graph.microsoft.com/v1.0/me -> GP works | PM works
Request to: https://graph.microsoft.com/v1.0/me/calendar -> GP works | PM don't work
Request to: https://graph.microsoft.com/v1.0/me/contacts > GP works | PM don't work
.....
(GP = Graph Playground // PM = Postman)
Token
On the left side we see the token created via postman. On the right side we see the token from Graph online. I can't find an important difference, you can ? :-)
I'm trying to explore the Google Identity Toolkit API using the Google API Explorer. The API hints that "No auth required", however when I try to execute a request there is an error message:
This method requires you to be authenticated. You may need to activate the toggle above to authorize your request using OAuth 2.0.
If I try to use the OAuth 2.0 toggle and Authorise the API I get a 400 error:
Error: invalid_request
Missing required parameter: scope
But Google Identity Toolkit API does not declare any scopes.
Please can someone help?
UPDATE:
Further errors I get when using the API Explorer: When trying to execute the getAccountInfo request, I pass a request body with the localId field populated. The response I get is:
400 OK
- Show headers -
{
"error": {
"errors": [
{
"domain": "global",
"reason": "invalid",
"message": "INVALID_SERVICE_ACCOUNT"
}
],
"code": 400,
"message": "INVALID_SERVICE_ACCOUNT"
}
}
Here is the list of Google API scopes:
https://developers.google.com/identity/protocols/googlescopes#oauth2v2
This completely omits Identity Kit.
Tying in a random string into the scopes box produces an error:
I have guessed up that the scope should be https://www.googleapis.com/auth/identitytoolkit by looking at the pattern.
And this scope does not cause an error. So this means it is a valid scope, even though it is undocumented.
That said, I used an API request of:
POST https://www.googleapis.com/identitytoolkit/v3/relyingparty/downloadAccount?fields=kind%2CnextPageToken%2Cusers&key={YOUR_API_KEY}
{
"maxResults": 999
}
And it produced:
200 OK
{
"kind": "identitytoolkit#DownloadAccountResponse"
}
So I will say that I have successfully executed this query while using an undocumented feature. However, it appears that the result from the server is incorrect.
This should answer your question, although the result is simply shining light on a broken server implementation.
I have not reported the bugs / undocumented feature in this answer and would appreciate assistance in that effort.
You may find how to use Google Identity Toolkit from the official site. If you really want to manually try Google Identity Toolkit API, you need to enable the API in your Google Developers Console project, create an ApiKey in the project, and call the API using a command tool like curl. The request syntax should follow the one shown in the Google API Explorer.
The google verification api is giving me a 503 error "An unexpected error occurred. Please try your request again." whenever I try to verify a domain using the TAG_MANAGER method.
This occurs when I try to use the API via the PHP client library and also when I use Google's API explorer. However, if I log in to Google Webmaster Tools and add the site, using Tag Manager as the verification method, I am able to successfully verify myself.
I've attached debugging information from the API explorer below, but it's very light on detail. My support request in the webmaster central forum has been met with deafening silence, but I'm not sure where else to ask.
Request
POST https://www.googleapis.com/siteVerification/v1/webResource?verificationMethod=TAG_MANAGER&key={YOUR_API_KEY}
Content-Type: application/json
Authorization: Bearer ya29.iAC-QBa-7nzvS2lpFFmfcej2Y0suhiWHgS8SivKN9jpYWffljsRV7rbL
X-JavaScript-User-Agent: Google APIs Explorer
{
"site": {
"identifier": "http://unit1-28leanyerdriveleanyer.com",
"type": "SITE"
},
"owners": [
"loboyle#raywhite.com"
]
}
Response
503 Service Unavailable
- Show headers -
{
"error": {
"errors": [
{
"domain": "global",
"reason": "backendError",
"message": "An unexpected error occurred. Please try your request again."
}
],
"code": 503,
"message": "An unexpected error occurred. Please try your request again."
}
}
https://www.googleapis.com/siteVerification/v1/webResource?verificationMethod=TAG_MANAGER&key={YOUR_API_KEY}
may need to be
https://www.googleapis.com/siteverification/v1/webResource?verificationMethod=TAG_MANAGER&key={YOUR_API_KEY}
also, a few additional notes
For Google to use your Google Tag Manager container snippet code for Webmaster Tools verification, the code must be placed immediately after the opening tag of your page.
The method you provided is used for verifying a site or domain, be sure you intend to verify a site, because this is what your request currently contains.
This method requires you to be authenticated (OAuth 2.0)
http://code.google.com/apis/accounts/docs/OAuth2.html
Ensure you have visited the following link
http://www.google.com/tagmanager/features.html
I finally stumbled across the fix for this today. The problem was that the service account running the requests needs to have "View and Manage" permissions on the applicable Tag Manager account, not just on the container that is actually being used. Only view access is required to the actual container.
While this isn't exactly desirable (we have 20+ containers for different sites/applications within the one account), it does resolve the problem and allow the Tag Manager site verification to work as intended.
I'm not sure whether the documentation has been changed since I originally had this problem or whether I just missed it. The required permissions are unexpected and the response code is misleading (a 403 would make more sense).
Check if you've enabled "Maintenance Mode" on your domain you're trying to verify using Google. Disable it and you're done.