We have an app, that works without problems on dev machine and deployed in cloud, but we are having problems setting it up on server in corporate network, where everything (e.g. views with information from database) except Forge Viewer and Forge API (e.g. upload) works.
It fails with a message "Underlying connection closed" when we are trying to get Autodesk Forge 2 legged token. We are using Autodesk Forge .Net SDK v 1.0.2.
We did additional tests and seems like all outbound API calls on the server are failing. I know there is not enough information to actually solve the problem, but I would appreciate ideas where to look for the solution.
Related
I am trying to connect and query our foundry ontology from different Microsoft tools in our own network. I was able to do so using a token as described in the documentation. That works great and it is easy to configure. The problem is that it is associated to only one account and the token expires often.
Reading the documentation I saw the option for OAuth. What is not very clear in the documentation is whether we have to register an application for ODBC and how to do it. When I have had to register applications in the past in cloud environments, the application normally has a returned address that the cloud app hits to authenticate. However, in this case, I don't see how that would help for ODBC from desktop applications like Excel or Access.
Any suggestion or reading would be appreciated
To use the OAuth flow with the ODBC driver on Windows you can register a third-party application in Foundry (see docs). You can use a public or confidential client, and the redirect URL should be set to http://127.0.0.1/foundrydriver/oauthredirect.
I want to ask about the Deployment of Forge API by Azure.
I had done it through the resource from Learn Forge, and it seems to work smoothly on the local site, but when I try to publish it, Although it shows permission
after I sign in, it shows 400 error refused, how can I do this for this error?
This is typically caused by an incorrect callback URL for the 3-legged authentication workflow.
When you develop your application locally, you typically set the callback URL (both in your application's code and in https://forge.autodesk.com/myapps) to something like http://localhost:3000/api/forge/callback/oauth).
However, when you deploy your application to Azure, AWS, Heroku, or any other cloud hosting provider, the callback URL must be updated accordingly. For example, if you deploy your application as an Azure Web App, the callback URL could look something like https://my-cool-app.azurewebsites.net/api/forge/callback/oauth. And again, you'll have to change the URL both in https://forge.autodesk.com/myapps, and in your Azure Web App settings.
Another question regarding design automation.
I am trying to deploy the app to AWS but it seems that the appsettings.json file is not coming throug and the result is that I receive an error saying that the cliendid parameter is null.
Can someone help me through this?
I don't know why appsettings.json didn't made it to your AWS but if you use Forge Design Automation SDK (https://github.com/Autodesk-Forge/forge-api-dotnet-design.automation), there is way how to setup ClientID and ClientSecret using environment variables.
Forge__ClientId=<your client id>
Forge__ClientSecret=<your client secret>
I know about xamarin connection with SQLite but it is locally
I need to connect my remotely MySQL database with xamarin.forms (I know about the security issue of this without using web services layer, but i will only use it for my own work)
This plugin is for xamarin.iOS and Xamarin.Android
I cannot add it using dependency service because i cannot add this component to the shared project
So is there any example of connecting MySQL database with xamarin.forms
You can't add references to your shared library. Shared libraries act like a list of files that are directly included in the project. The advantage of shared projects is just, that you do not have to maintain these included files for each project that uses code of the contained files. See the Xamarin documentation for further explanation.
What you have to do, if you want to consume a 3rd party libray within a shared library: Add the library to each project that uses the shared library (e.g. your iOS and Android project)
2ct to the mentioned security issue
You are right about the security issue. That's why I'd advice against, using mysql directly from your app. (I'll explain it for other readers that aren't aware of this problem and stumble over this question)
You should tunnel it through HTTPS because:
Some networks just block certain ports (HTTP and HTTPS are usually not blocked)
You publish your credentials with your app either statically or dynamically, but the credentials to your database are interceptable either way. You should authenticate a user and not an app. So there should be some kind of authentication / authorization that is revokeable. There was a nice talk from Kerry Lothrop on the Xamarin Evolve 2016 on this topic. https://www.youtube.com/watch?v=uLFtQHNxGaI
I am in the digital signage business for small businesses. We have created an app that runs digital signage through the raspberry pi using Windows iot. Everything works great but what if one day we wanted to make changes to the app. Is there a way to update the app without having to manually do it on site. I would prefer having the app do it programmically through regular checks but I'm not finding anything. Wish there was a App Store mechanism for the pi to update apps. Any ideas on this?
All devices running Windows IoT Core run a small webserver instance on port 8080. You can reach this by visiting http://DEVICEIPADDRESS:8080
The default credentials are:
U:Administrator
P:p#ssw0rd
Within the portal, you can provision and deploy apps remotely using the App Manager by selecting "Apps" along the left-hand pane.
If you setup firewall rules to allow outbound traffic to the Windows IoT Core device you may be able to deploy updates remotely.
Currently there is no app store for windows iot but it is possible to create your own. You could implement this functionality using a push or pull system with Azure.
Push - azure pushes updates to the devices.
Pull - the device asks azure for updates
Get started with Event Hubs (tutorial describing how to implement Event Hubs in Azure)
Another option could be to write your own REST API on a server (Azure or your own server).