Trying to create some custom behavior with Zapier, and the app framework just doesn't fit. All I need is a one-off token to paste into my Zap. Can you add like a "generate new token" feature on projects and organizations, please?
Authorization with for the QuireAPI is based on the OAuth2 standard.
From the related docs it looks like Zapier supports this as well.
Please consider using the more flexible Oauth2 flow over a "convenient" on-off-token.
UPDATE: new feature discussed in quire-api#26
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.
We used to be able to create GitHub personal access tokens via a request to api.github.com/authorizations with the username, password, and specifying the token’s scope. That functionality has been deprecated as of November 13, 2020.
It seems nothing took its place. They recommend the web application flow, which makes no sense if you’re building a CLI tool.
Rather than asking people to go to https://github.com/settings/tokens to manually create a new token, is there an alternative which works by not having to leave the CLI?
For that use case you should consider using "Device Flow". Documented here.
I'm trying to create a bot in a sharepoint site. To do that i need to retrieve the user info using implicit flow authentification method, however i haven't found any example using .NET and all the examples are in Node.js.
Can someone show me how to do that please ?
There are a number of .net examples online:
https://stephaneeyskens.wordpress.com/2017/01/04/microsoft-bot-framework-transparent-authentication-with-the-webchat-control/
https://github.com/Ellerbach/SharePointBot
https://www.rickvanrousselt.com/contextual-authentication-webchat-control/
https://www.linkedin.com/pulse/chat-bot-luis-sharepoint-part-one-akshay-deshmukh/
However, they are a little dated. Just this week, Microsoft released a new integrated OAuth feature for bots.
One of the Service Providers is Sharepoint:
What are the basic functionality which it provides?
Specifically for the person who has never used asp.net built in stuff.
The MSDN tutorial is confusing me a lot. Claims, OWIN,etc are going above my head.
What I can make out of all this is - The Identity framework helps me to manage my application plus social logins. It handles my cookie,etc.
What if I have just one role in my application - just the plain user?
Should I go for the Identity then or I should implement my own custom thing?
Any help is appreciated.
If you are starting from scratch, build a sample MVC project with individual membership option, which will create the following components for you:
Login module that creates and manages authentication cookies
Simple database to store basic user data (credentials, name)
EF code to interact with the database
This will most likely meet your use case for a user without roles and attributes.
OWIN really has nothing to do with authentication, it is a new spec for building web apps. The login module happens to be implemented according to this spec and it sounds cool, so Microsoft likes to throw this term around a lot.
If you are not planning to have authorization logic in the app, then you don't need to worry about Claims. Claims is another term for user attributes (login, name, roles, permissions). The Claims collection will be populated by the framework, but you most likely won't use it. If you need just the user id/name, the old ASP.NET interfaces are still there to get this data.
As far as implementing your own, I've seen people here ditching the database and EF code, especially if they already have an existing user store. You just need to implement a credential verification logic against your store. You don't want to build your own cookie management, though. Use the login module provided by Microsoft or well established third party systems (SiteMinder, Tivoli, etc.)
Looks at this open source project for a good alternative to ASP.NET Identity.
This is a very well put together tutorial that explains many of these concepts, you can get a free trial to the site to see it.
I was poking around Google's analytics API docs to see if there is a method that allows the adding of website profiles. Either by using a email/password or session or one time token. Has anyone seen anything?
No, I don't think there is a way to programmatically add a profile. They do have a good API for reading the data in an existing profile.