I'm working on 3 apps simultaneously. When I login in:
"https://dev.buildfire.com",
only one of the app's ID appears.
How can I login with another app ID?
The website dev.buildfire.com, aka the "developer portal", is used to manage your custom developed plugins. Alternatively app.buildfire.com, aka the "control panel", is what you use to manage your apps. If you want to manage your apps just login into the control panel and select which ever app you like.
It might help if you describe what specifically you are trying to do.
Related
I am trying to implement the clickwrap process and am using the php SDK.
When going through Auth via the Authorization Code Grant method and as part of the process it is asking for a login before completing the process. I've used my dev account details however why is this step needed as we are already passing through various keys/id?
Is this specific to the development environment or will this also happen in prod?
What will be presented to the end-user who does not have a Docusign Account?
I understand the 'obtain user consent' and can work that into the workflow but this is confusing.
I have worked through the Quickstart app as well and that has the same process. Have I misunderstood something?
If you want a page on your application to include a DocuSign clickwrap agreement, then you do not need to use the Click api. (It really should be named the Click Management API.)
What you do: follow the instructions for adding a clickwrap agreement shown in the Click User Guide.
The Click Q & A page is also helpful.
The "Click API" is only needed if you want to programmatically look up the Click agreements, modify the Click configuration, etc.
If you're just building an app that would ask for user to agree to a clickwrap using DocuSign Click, you won't need the end-user to authenticate.
I suggest you look at https://myclickwrap.sampleapps.docusign.com/myclickwrap/ and the code in GitHub.
Your app needs the creds to make API calls, but you could use JWT for example with one-time consent and your APP will not make these API calls on behalf of anyone, but just for the one user that the account uses.
All of this is the same in the developer env or production.
I'm working with actions on google and dialogflow, and recently they proposed google signin to make account linking fast without writing own oauth server.
Today I implemented their google signin in my dialogflow app it is working quite fine but unfortunately I am unable to delete that account to check all development aspects, I tried my other google accounts and my friends account but soon ended up out of accounts
Un other methods when i enable and disable testing it forget about linking but in google signin it is tightly stick with the account, and i have tried almost everything i can try like restarting my phone and clearing cache of chrome browser but it looks like it is saving account somewhere in cloud.
What i need to do is, when i sign in first time it ask for name permission, i need that screen again and again for testing something
Google calls this Removing a Website or App that has access to your account. It is done using the myaccount.google.com console.
If you want to do this using Android, the easiest way is to:
Open your device's Settings app Settings app and then Google and then Google Account.
At the top, tap Security.
Under "Signing in to other sites," tap Signing in with Google.
Tap the name of your project.
Choose Remove access.
Through the web, you can go to Apps With Access to your Accounts:
Scroll down to the "Signing in with Google" section
Locate your project.
Select it, and choose "Remove access"
The name that is shown should be the name you've given to your project as part of the OAuth screen. If you haven't set that up (and if you're just playing around, you probably haven't), it will use the Project ID for your project. You can find this on the Cloud Console home screen attached to the same project name that you used in Dialogflow and the Action Console.
While you're in there, you will probably want to configure the OAuth screen to have a name for the app as it will be visible to users on the OAuth screen. From the menu, select "APIs & Services" and then "Credentials"
Select the "OAuth consent screen" tab, and fill in the "Application name".
This name should then be in the list of applications you have installed, and can remove.
I want to build a web api to deploy to Azure so that I can call it from a few separate web apps to collect user input.
The users wont be logged in, but I want to ensure that only the web applications can call the api. Thus I need some kind of authentication, and I am trying to understand my options.
In Visual Studio 15.5.4 I selected New Project-> Web-> Asp.Net Core Web Application->Web API
I am wondering how ensure that only my web applications can call the web api.
I tried clicking Individual User Accounts and was surprised to find a combo box with only one option/
Have I missed a setting somewhere for there to be a combo with only one option?
If I choose Work or School Accounts instead then there is another single option combo
The combo population for the Domain combo depends on my being logged in to Microsoft, and consequently the Active Directory domains that Azure can find associated with me.
Then using the Web Application template and work or school accounts then there is a choice of Cloud-Single Organization and Cloud-Multiple Organizations.
If I am using the Web Api template then only Cloud-Single Organization is available.
I am developing a web portal using Angular JS and node.js and I have been researching to find a library in node.js which provides role based access control.
All the libraries which are currently available such connect-roles, ACL etc provide page level authorization where you cannot access a particular path or URL based on your role.
Do we have any ready made options where in we can enable/disable a text box based on the role of the user? So my page page will be rendered to the user however some of the fields will be disabled based on the role of the user.
Thanks in advance.
You could give below a try
The above is part of ongoing Node.js boilerplate platform below
Nodejs_Postgresql_VanillaJS_Fastify
Was wondering, once I submit a concept and it is approved, whether I am able to test my app with real Spotify users before submitting it for general availability. If so, how would I do that? I'd expect I could have a page that people can accept the conditions and click to accept, then it would install the app in their installation but it would not be visible in the general app store. Is this possible?
Currently there is no managed test environment available. If you want to test the app, you have to distribute the app bundle manually and ask the Spotify user to get app developer permissions on developer.spotify.com