As per this doc, in order to create a connector to Microsoft Teams, I'm supposed to publish it to the store.
If I am to build an internal-facing, highly company-specific bot that notifies of specific events, which is obviously supposed to be private, is there a way of building it?
Am I missing something here? Is it really necessary to publish it to the store in order to have it working in my company's Teams account?
As per this helpful link,
When you're ready to share your Microsoft Teams apps, you have three options depending on who your target audience is.
Upload your app directly If your app only needs to be shared to your team, or a few individuals in your organization, you can share your app package and upload it directly.
Publish to your organizational app catalog You can share your app with your entire organization through your app catalog.
Publish to the public app store If your app is for everyone, you can publish it to our public app store. Depending on your goals, you might be eligible for marketing and sales assistance.
So, in this case, uploading the app directly is the answer.
Related
I would like to start a new e-commerce platform build with Shopify/Hydrogen (React) an I'm still not sure about the back-end side (maybe ExpressJS + DynamoDB).
The issue is that I want to host everything on AWS, I am new there and I don't really know in which direction should I go.
Basically the platform is created for selling fishing stuff but it should also support the drop-shipping context, where other companies can sell their own products there.
Can anyone help me with a path for achieving this? What are the right steps?
Regarding headless storefronts you have multiple options with hosting, starting from Gatsby Cloud, through Netlify, Vercel or Amazon Amplify in case you want to host it on AWS.
I will assume that "drop-shipping context" would mean you want to become a some sort of a marketplace? Where other merchants would list their products and upon purchase handle the shipping themselves? You can organize that through using free open-source CMS - Strapi in a manner where it acts as a PIM (product information management system), basically you will create users in admin panel and allow them to put products into CMS and then pull and publish them to Shopify storefront (through Admin API you can even create products and add them to an order on the fly), also through webhooks that Shopify trigger on the purchase event you will be able to send a notification to a dropshipper.
Regarding Hydrogen it's pretty early in the making so I would suggest to take a look on React-powered boilerplates out on Github and it will boost implementation speed significantly.
Assume that there is an application, SPA, that uses Google OAuth2.0 to access the Google Drive API.
Reading the docs, the application flow seems familiar enough on the client-side specially with Google's JavaScript library for authentication. However, I have stumbled upon a roadblock during application registration phase.
When creating the credentials for our client application, I am redirected to fill out the form at the OAuth Consent Screen first. There, among other things it demands us to declare whether the application is in Testing or In Production phase, so it can decide whether the app will be available to everyone or to Test Users only.
Assume I create a project for our application and set it on testing at first and then change it to production once I am ready to publish (with a new set of credentials as well).
My question is this. What if development continues on the application for new features while one instance of the app is in production? During development and testing I would need to restrict the application to my Test Users alone. Since the OAuth consent screen is project specific, not credential specific, will I require multiple projects on the console for every environment in which the application is running?
As in,
Project MyAppTesting will permanently remain in testing mode and will denote our development/testing branch.
Project MyAppProduction is always in production and denotes my production branch.
Similarly for the mobile client:
A MyMobileAppDev project having credentials configured with the debug keystore hash
A MyMobileAppProd project having credentials configured with the production keystore hash.
(both sets of credentials share the same package name).
Is this the idiomatic way? I failed to find any documentation on the matter. Please advise.
What #JohnHanley stated is the best way and the best practice when deploying application/s in GCP.
You can create multiple projects and create different Oauth for each of the projects. Check out this link on service accounts.
In addition to that, there are also some pros and cons when it comes to billing.
Pros:
Users consider having multiple billing accounts with respective projects assigned for each account to be able to see their billing details separately. In this way you can monitor the billing for each of the respective projects for each account.
Cons:
Attaching all the projects to one billing account, however, the billing reports will show all of the sum of the cost for all the projects, but you can still use the filter menu to be able to see the charges for each project.
I am developing a web app which will be pulling data from Amazon Advertising API. I need as a user to see data for all of the sellers that has approved/registered for using their profile's data.
Is this scenario possible? If not, is there anything similar to it? If yes, how do I implement it, is there some documentation?
The Amazon Advertising API v2 was released late 2018, so it's pretty new but has some missing information in the official documentation. But to get started please follow the official documentation guide:
https://advertising.amazon.com/API/docs/v2/guides/get_started
A lot of other sources are outdated, so I suggest to stick to this guide.
The logic to handle multiple Amazon Seller Accounts you have to handle yourself.
But every Seller Account has to go through the consent workflow to give your console app the rights to get access to the shop data via API. Therefore you need to implement a 'Login with Amazon' button - That's the part that is not mentioned in the documentation. See https://login.amazon.com/
Essentially, I'm wanting to create an Oauth Client as an App so I can get data from Dynamics for multiple customers. Does anyone know if this is possible to do in AppSource or do you know of another way?
I have a service that will be served in a cloud different than Azure so there really isn't anything for me to submit as an App and I really don't want every customer to have to setup their own App that gives my service the privileges/access it needs, but it's looking like I may have to.
It sounds like you'll want to register an app with Azure AD (the OAuth2.0 service/identity provider for work and school accounts), and create a multi-tenant app. Then you can configure this app in the Azure Portal to get permissions to the APIs the app wants tokens to call (in your case Dynamics or the Microsoft Graph).
Once this app is written, you can code up your app using one of the Azure AD Auth Libraries. Here's some sample code for a .NET web API. You can find more code samples on Github and search active directory. Moreover, the Azure Active Directory Developer Landing Page is a great place to look for more resources on doing all of this.
Background:
I'm building a small application that will be run daily, pulling data from our own in-house databases and sending it over to our corporate Salesforce instance. I've built a custom object (called Marqui_Instance) in our Salesforce instance to house the data. The app will be creating a couple hundred of these, and attaching them to various Account records.
The Problem:
Our Salesforce instance is Professional edition, which means I can't generate the WSDL for our instance, which makes me think I'm not going to be able to develop code that can create/edit/delete Marqui_Instance objects.
Before I start floundering around in the dark, I thought I'd post on here for advice. The only thing I can think of is to create an identical object in a Salesforce developer account, and use the WSDL from there... but then when I go to deploy the code in production, will it work? I'm scared that the WSDL from my dev account will have some guids or something similar, and my code will only work against the dev account.
If you get your application certified by Salesforce they will provide you with a "Partner Application API" token. Using this when establishing the Salesforce API session will allow your application to work with a professional edition org.
Alternatively, you can also obtain API access to a Professional Edition org by paying an additional fee. You will need to contact your salesforce.com sales person.
Update: Apparently the functionality is enabled by Salesforce internally using the informally named "Black Tab".
See also: Re: Use of the API and Salesforce.com Professional Version
Access to the web services API for Salesforce is only available in Developer, Enterprise, and Unlimited Editions.
I believe that you aren't allowed to login to the API, so even if you managed to generate a WSDL it wouldn't work.
See the full edition comparison chart [PDF].