Zapier OAuth2 Docs update #375
Conversation
en/plugins/zapier.md
Outdated
|
|
||
| 1. Giving a third party app credentials to your Mautic is a security risk. If something happens you simply delete this special Zapier user and your admin user will be safe. | ||
| 2. You will see what contacts were created by Zapier simply by looking at the created by user. | ||
| Once you choose to use Mautic integration you'll need to authorize your Mautic to it. |
There was a problem hiding this comment.
Once you choose to enable the integration, you will need to authorize Mautic to communicate with Zapier.
There was a problem hiding this comment.
I've made a few minor suggestions - please also take a look at https://github.com/mautic/documentation/blob/master/CONTRIBUTING.md for our guidelines on documentation and give me a shout if anything is unclear!
|
@RCheesley I see. Thanks |
|
@escopecz How we handle with basic auth info. Should remove it, or just notice about changes from basic auth to oauth. Or let setup also for 2.x (basic auth) and 3.x (oauth2) separately |
|
I guess we can remove it. The question is whether we want to wait with the Zapier Oauth2 PR till we fix the refresh token expiration or add to the docs to increase the refresh token lifetime to some big number. |
|
@escopecz that refresh token expiration should be updated on every access token generate. That means, app stop working just If there is no usage during that expiration (default 14 days). Should we add just note to docs? |
|
@kuzmany you don't sound confident :) You said a customer of yours already runs this version. There are no problems with timeouts? Is their expiration value default at the Mautic API configuration? A note in the docs would be great. |
|
@escopecz It was bug, we didn't store updated refresh_token. But at the moment looks good. I did few tests |
mautic/mautic-zapier#18