I am implementing an integration with Google Drive, which is to show a user's Drive files on our own website (after a 3-legged OAuth2 authorization).
So it is not a webapp that you will connect to the Google Drive UI, and thus I don't see the need to publish it in Apps Marketplace.
My project is created with my personal (free) account on console.developers.google.com,
and I'd like to confirm here: if not published, will it still work with any types of accounts, especially with enterprise accounts(e.g. Google Apps for Work)?
It does not need to be published as long as the domain administrator has not disabled Drive Apps. If a domain admin has disabled Drive Apps, I believe publishing to the Google Apps Marketplace is required so that the domain admin can install the App for all domain users.
Related
Do the updates work if the app is installed with a different account but is currently logged in with own account?
I would like to deliver the Android devices with my pre-installed app and the devices will receive updates later if the customer logs on with his own account.
They will work, but this kind of installation is not recommended and could be consider a security risk and Google may notice that one account has logged on numerous devices and block the account.
it is better to install the app via APK file without logging on with any account. you can get an exact Google Play APK from Google Play console.
we are running a trading B2B platform were we cannot create testing accounts on a production environment.
Currently we are trying to submit an app to the Microsoft teams catalog, the submission process asks for test credentials to be used to test the app and the connection to the platform alongside the manifest file. however we can only provide sandbox test accounts, which will obviously cannot be used in the production app, and are hosted under different links.
in the manifest to be submitted we setup the production links for the app that needs to be submitted to the store.
The question here is how is this usually handled? how should we provide a sandbox test accounts and a production manifest at the same time for the app submission process?
Basically what Microsoft is asking for is credentials to a test Microsoft 365 tenant, where they can log in and install your app. Your app must for sure already be 100% "production" ready - live hosting etc., not a test setup behind the scenes.
I am using Microsoft Graph API to send messages to private users in Microsoft Teams. I registered an App in Azure Active Directory, gave proper permissions and called the API and was able to successfully send the message.
My question is what would be the most efficient way to deliver this integration to different clients? Do we have to register an App in every azure directory of the client individually, or is there a way I can publish the app that I have created with all the API permissions required and the administrators can install the app in their azure directory
You would have to publish your application in your home tenant as a Multi-tenant application.
When a user from the client's tenant access your app, they will be prompted for login and post that either the user or an admin will have to consent to the app and the required permissions. This will create a service principal in the corresponding user's directory where the consent objects are stored. This way you don't have to register application in each directory.
You can follow the steps listed here for more detailed instructions to convert your application into a multi-tenant app.
in my account the google drive api is disabled but still when I authenticate a thirdparty app using oauth2.0 it can access my drive files. Then what is the use of this enable api.
Cloud developer console is a place for developers to create applications. when you create a new application you must decide which APIs will be used by that application.
I authenticate a third party app using oauth2.0 it can access my drive files
Unless you are the developer of the third party application setting this will not have any effect on what applications created by other developers can do with your account. If you dont want them accessing your drive account then dont install any third party applications that request permission to access your drive account.
I've created my action on Google development project and I've deployed a self signed service locally(in the local network) which I've added for fulfilment on the Action settings. Now I see my app in the Google Assistant, under Add devices, but when I try to link accounts(the account linking was also set previously), the action.devices.SYNC is not triggered and I get the "Couldn't update the settings. Check your connection". My phone is also in the same network. What am i missing?
All Google Assistant Actions, including Smart Home Actions, go through Google's cloud. Even requests from your phone or Google Home device to the smart device on the same LAN go through Google's servers.
Google's servers need to be able to contact your local service, so it needs to have a globally accessible IP address/name.