Is it possible to host an Azure Mobile Service? (Published on my own server)
I only want to use the Mobile SDKs to sync tables on mobile applications, I don't need push notifications.
I also want to have a Web API controlling this data in the same project, is it possible without having NuGet Packages problems?
Other question, do I need the Azure Mobile Backend to make it work with the Mobile SDKs (iOS, Android, etc)?
If those solutions don't work, I'll be hosting this on Azure and probably managing the data with another Web API self-hosted.
You may want to consider Azure Mobile Apps which allows full control of your deployed site.
The Mobile Services backend, or Mobile Apps server SDK is required for the Azure Mobile client libraries to work.
Related
I have been trying to create a Flutter app that uses SSO with my freshly made Microsoft Azure account. I have decided on oauth2 dependency, but I'm not sure what to put in redirect() and listen() methods.
Also, does my Azure App need to be web or mobile based? Any special tweaks?
Do I need a local web server running since it's accessing localhost?
I have a Raspberry Pi3 device which has Android Things dev preview 0.6.1 installed. On completing certain operations, the device needs to send data to Google Cloud Storage. To do so it must have an API key to authenticate itself.
In Android devices it could be done easily using by integrating Google Sign in Option but since my Android Thing device doesn't have any interface, Google Sign In could not be implemented in it.
I have gone through github project Android Things Weather Station Sample which is using Google Service Account to publish data to PubSub. To do so, it generates and imports a credential.json file into the project and somehow generates credentials from it.
So my question stands is, without user consent, can we use Google Service Accounts to authenticate with Google Cloud Storage? If yes, how can we generate access token from it ? If no, is there any other method to authenticate with GCS?
The simplest and most secure way to authenticate your IoT devices with Google Cloud is using Cloud IoT Core to publish data over MQTT or HTTP into Cloud Pub/Sub. Cloud IoT Core is a bridge designed to securely manage large fleets of devices and authenticate them with your cloud project.
Take a look at the SensorHub sample app on GitHub, which is similar to the weather station, but uses Cloud IoT Core to authenticate and publish instead.
As Shubham stated, using a service account is one way to authenticate devices. Otherwise you'd need to build a mobile companion app which you use to authenticate the user. Then you would have to transfer that token to the IoT device.
In case anyone faces the same issue, I found this document which has explained the way to authenticate devices with Google Cloud without the consent of a user.
I have a Webapp hosted on Google compute engine. I am trying to list it on Microsoft AppSource. One of the mandatory conditions for listing is enabling Azure Active Directory federated Single Sign-on (AAD federated SSO) for the app.
Google Cloud platform supports SAML 2.0-based SSO. Hence technically this should be possible. Has anybody tried it and any has experiences to share. Thanks in advance.
In order for an application to integrate with Azure Active Directory - it is not required that you have an Azure Subscription, or even Azure Active Directory (specially if your application is a multi-tenant application) - you can host your application anywhere.
For AppSource, as long as your app integrates with Azure Active Directory, then you are able to list your app on AppSource - which means that the application does not need to be hosted in Azure. AppSource also requires Open Id Connect - SAML would not qualify. For more details please see this article.
To make it easier to test the Azure AD integration in your application, you can create/ use a test tenant with a Microsoft personal account (MSA), as well as use this MSA account to register your application for OAUTH2 flow.
You probably don't want to use GCP's SSO. This is really designed to allow your developers to use your organization's auth system while working on GCP. This is different than allowing your users to use their organization's AD while working within your web app.
Instead, I suggest you look to see if anyone has built AD or SAML integration for the framework your webapp is built with, or look to implementing it yourself. This allows the SSO auth to be used for the app itself, instead of in accessing GCP APIs.
Azure App Services Mobile Apps can provide a Custom API hosting service which looks very similar to API Apps.
What is the real difference between the two?
Is it possible to consume Mobile Services from API Apps Node Backend ? Is there any Mobile Apps SDK available for NodeJS ?
https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-node-backend-how-to-use-server-sdk/
Azure API Apps is for hosting APIs that will be consumed from a variety of clients, and where it is acceptable to codegen a client, or make direct REST calls.
Azure Mobile Apps defines a client and server SDK with a protocol for communication that adds additional functionality for things such as offline sync. Offline sync is not possible with API apps, because there is no actual client SDK, just tools for generating one for different platforms.
I have an exixsting windows 8 app connected to an azure customdb, shared with a web app, using azure mobile services.
I would like to write a new version of the app for windows 10 using azure app services, but I don't find documentation about the changes using a custom existing db.
Where can I find it?
The changes to the database between Azure Mobile Services and Azure App Service are identical. If you want a tutorial on how to use an existing table and project it into mobile apps, I wrote one here: https://shellmonger.com/2016/05/11/30-days-of-zumo-v2-azure-mobile-apps-day-19-asp-net-table-controllers/ - it's part of a sequence of posts, so you may have to go back a couple of posts to get to the start of the ASP.NET ones.