Connector Improvement: API auth via API key instead of username/pass
Answered
Hi, I'm Nick, Sys admin @ Scopely. We have users that integrate Fivetran with MailChimp and the connection is authorized with a personal account user/pass which isn't best practice. If the user leaves, account is removed, API connection breaks, needs to be re-authed.
I know we can generate API keys on the MailChimp side....but in Fivetran documentation for connection with MailChimp, it states the following:
Authorization: "This type of connector can only be authorized through the Connect Card or through the Fivetran dashboard."
So Fivetran <> MailChimp connection doesn't appear to be possible via MailChimp API key and we'll need to create, (pay for), and use a service account for this auth connection..
Would be great to add API key support for these sort of connections!
-
Official comment
Hi Nick, thanks for writing in! I agree, re-authing is a pain, and tying it to an account where you can better centrally manage API keys and their rotation is generally a superior experience. I'm going to add this to our backlog.
How often do you run into re-auth issues on average?
Thank you!
Jimmy
-
Jimmy -
TBH, just gained admin access to this system help the team re-auth this connection. But just knowing how things can go, as users come and go, having an connector auth'd with an individual account isn't great as the user may leave and their fivetran account could be deprovisioned which would break the connection. API keys is just a personal preference but I was able to auth it via user/pass with our service account. So that works too.
Please sign in to leave a comment.
Comments
2 comments