OAuth 2—How It Works, Refresh Tokens, and the State Parameter

By Daniele Timo Secondi

At Pipedrive, we work hard to provide salespeople with the best CRM to manage their workflow. At the same time, we know a sales CRM is often used together with a variety of other tools, which can be different for each company. So we created a marketplace where other developers can create apps and integrations to cover those needs that salespeople have, but we don’t cover natively. So, for example, if you want to use MailChimp for your email marketing, you can connect it to Pipedrive by installing one of the available apps on the marketplace, and have your contacts synced between the two platforms. One of the technical questions to answer in this kind of scenario is, how do you give these apps access to the user’s data in a controlled way? You probably guessed it. The answer is with OAuth 2.

This article was originally published in the March 2019 issue of php[architect] magazine. To read the complete article please subscribe or purchase the complete issue.

Leave a comment

Use the form below to leave a comment: