Problem
We created an app under an active trial account.
We added this app to the BIM 360.
We use this app properties to access model derivatives.
We get authorization error while accessing the model manifest.
{ "developerMessage":"You are not allowed to use this API because your Forge trial is expired.", "moreInfo": "https://forge.autodesk.com/en/docs/oauth/v2/developers_guide/error_handling/", "errorCode": "ERR-004”}
We call next method
https://developer.api.autodesk.com/modelderivative/v2/designdata/URN/manifest
Why we get message about "trial is expired" if it's not?
Possible reason
Something went wrong during the trial account creation.
If you go to forge.autodesk.com > Forge Account Details > Cloud Credit Balance > Active Trials, you will see progress indicator and no details.
Workaround
Create or use another one account and check Active Trials page. If you can see "days left" and "credits used" info, then everything must be ok.
Related
I had a trial account and the paid APIs expired, then I bought a subscription which was setup in the last day or so. But, when I call to transform a drawing (simple AutoCAD drawing in a bucket) I get the error below.
{
"developerMessage": "You are not allowed to use this API because your Forge trial is expired.",
"moreInfo": "https://forge.autodesk.com/en/docs/oauth/v2/developers_guide/error_handling/",
"errorCode": "ERR-004"}
please advise. My account in account management does show that I have an active subscription, and I see 100 credits allotted to my named user account. Application Client ID is shown in the image below
this appears to be working now. I do not know if something got jiggled on the backend or not, if so thank you!
I have just followed the tutorial video here:
https://www.youtube.com/watch?v=QOm0dHgwvbM
And after starting a trial on a newly-activated Forge account, have I thought followed every step in the .NET instructions to the letter.
However, when I run the application, and attempt to upload a file, I receive the following error on the Console:
An unhandled exception has occurred while executing the request.
Autodesk.Forge.Client.ApiException: Error calling GetManifest: { "developerMessage":"The client_id specified does not have access to the api product", "moreInfo": "https://forge.autodesk.com/en/docs/oauth/v2/developers_guide/error_handling/", "errorCode": "AUTH-001"}
Does anyone have any suggestions on how to remedy this?
Thanks,
Alex.
Did you select the Model Derivative API while creating an app in https://forge.autodesk.com/myapps? If not, please go there, then edit the app, select Model Derivative API, and save the change. Afterward, restart your .NET app to fetch a new access token.
ref: https://petrbroz.github.io/forge-samples-docs/#provision-access-in-other-products
So, it turns out my issue stemmed from having previously setup a FORGE_CLIENT_ID and FORGE_CLIENT_SECRET system variables on a previous, unsuccessful trial of Forge. This meant that the Visual Studio solution I created was reading those values instead of the ones I had input in code. Thanks to Cyrille Fauvel of Autodesk for helping me figure this out.
Cyrille says he is going to feed back to the rest of the Forge team that they ought to report back on the console the details of both ID and SECRET to prevent this happening in future.
We are occasionally seeing an issue with some projects where, when we try to do a GetPublishJob on a BIM360 model, we get back a 403 error, like this:
{"jsonapi":{"version":"1.0"},"errors":[{"id":"ad23cbc6-dc82-4dfd-83f9-6acd14bac6d2","status":"403","code":"C4R","detail":"Failed to get publish model job"}]}
In the docs, it says it could be whitelisting or permissions. We know our app is whitelisted, because we would not have made it this far if it wasn't. We're using 3-legged OAuth, and we believe that the user is able to manually perform the Publish. Can you tell us what specific other permissions might need to be investigated?
I am not typing answer, while I want to check some information with you:
if what you are using is this endpoint, it is public, so it does not need whitelisted. https://forge.autodesk.com/en/docs/data/v2/reference/http/GetPublishModelJob/ .
Since you are using 3 legged token, I doubt it may due to the expired token, while normally it should be 401 error.
With the same token, can your code perform Publish Model?
https://forge.autodesk.com/en/docs/data/v2/reference/http/PublishModel/
was this workflow working well in the past? or just failed recently?
To use this endpoint, the logged user (for 3 legged token) should have access with the folder.
We have already successfully configured the API Key but we keep getting the error error See You have exceeded your request quota for this API. Do I need to enable the billing for this?
This is the link that has error
Upon checking the site, the error was related to having no billing account, to fix the issue, kindly create a billing account in your GCP Console and associate the billing account to your project where the API key you're currently using belongs. After associating a billing account, your map should be working fine.
In addition, please note that you can only call a single API request if you don't have a valid billing account associated to your project.
I am attempting to set up an application using the Google Calendar API. I set up all the credentials and set the authorized JavaScript page equal to http://localhost:8000 as suggested within the quick start guide at https://developers.google.com/google-apps/calendar/quickstart/js. When I try to run the file on localhost:8000/quickstart.html it will show the basis page but no information. I can click the authenticate button and it will allow me to authenticate my account to use the Calendar application, however nothing will show up information-wise. Checking the console, the following errors are present:
Get https://content.googleapis.com/calendar/v3/calendars/primary/events?maxResults=10&orderBy=startTime&showDeleted=false&singleEvents=true&timeMin=2017-08-11T20%3A58%3A29.156Z 403 ()
and
Uncaught {"error":{"errors":[{"domain":"usageLimits","reason":"accessNotConfigured","message":"Access Not Configured. Calendar API has not been used in project 440480151645 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/calendar.googleapis.com/overview?project=44080151645 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.","extendedHelp":"https://console.developers.google.com/apis/api/calendar.googleapis.com/overview?project=44080151645"}],"code":403,"message":"Access Not Configured. Calendar API has not been used in project 44080151645 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/calendar.googleapis.com/overview?project=44080151645 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry."}}
However, going to the supplied link only says that I do not have access to the calendar.googleapis.com api and will not let me enable my Google Calendar or use it.
Google calendar uses Oauth2.0 for authorization. There are three essential components of this. If any of these are missing, authorization will not happen properly and you'll get a 403.
Access token - the google calendar API saves an access token to your
/.credentials folder by default. Your application will need to be
able to read this file (wherever it may be), otherwise you will have
to manually authorize API calls with every request.
client_secret.json - this is a necessary file to authorize your
application itself as a client of google. When you created a clientID and such using the google developer portal, this file was
created, and must also be read by your application.
Scopes - The scope is what level of access you have. It is by
default in the quickstart set to "read-only", which could be why
you're getting 403. If you want to change the scope, you're going to
have to edit both the line of code in the quickstart and either
modify the access token or get a new one to reflect that change.
I have gotten this error before, but that was before I understood Oauth2. If the problem isn't in any of these, it's likely something that you selected in the developer console. Let me know if you are still stuck.
Based from this thread, try setting the Referrers to Any referrer allowed for your project (just leave the field empty) in the Google Developers Console if it is not already like that.
To do this, go to your Google Developers Console and open API & Auth / Credentials and click Edit allowed referrers empty the input field.
Additional reference:
Google Calendar API v3 Access Not Configured
403 error with message:Access Not Configured. Please use Google Developers Console to activate the API for your project
Access Not Configured. The API (Google+ API) is not enabled for your project. Please use the Google Developers Console to update your configuration