I'm developing an app that makes usage of the FB graph api, more specifically the groups end point. With the new regulations over the permissions in April + the review process, I decided to use the "test app" process to test the implementation, but I can't find a way of how to install my test app on the groups created on my test users generated for my app. Is there any standard process for that or I need to publish my production app in order to test the installation in a group?
Related
I want to use Google Business Profile APIs to get data about my business into a BI tool.
I've created a blank project, create an OAuth consent screen, and created some Oauth2 credentials. I've managed to connect just fine but getting a message during the connection to say the app is still in Testing.
Do I need to publish the (practically empty) app that I'm using, or can I keep it in testing permanently? What's the pros/cons?
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 working on a project which needs to be integrated with Gsuite.
I am using .NET Core & EF Core for my project.
I have no idea how to integrate Gsuite with my application.
I've done lots of script that works with Google API's but I put all it needs manually(service account json file etc.).
Now, I want to make an application where users clicks the integrate with gsuite button.
Here is the scenario:
1) User clicks the "integrate with gsuite" button.
2) A service account is created with needed scopes in their GCP.
The result should be like this:
Any suggestions? Thank you.
I was developing a web application which shows posts from specified pages. While development I used "Graph API Explorer" App to test the application as it always returned a permission error when I try to use my App. Since few days back they have removed "Graph API Explorer" App from Graph API Explorer. I understand that we need Special approval to use Facebook pages API. But to get that approval we have to show a screencast of our application. So first we have to develop the application. But we have to test API requests while developing and there is no way to do that now.
Could someone please guide me how we should develop for facebook pages API. How we should test. Is there any specific dev permissions available.
Thank you.
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.