Connector Improvement: HiBob
Not plannedRequest: Add support for authenticating via a Service User (https://apidocs.hibob.com/docs/api-service-users).
Currently the HiBob Lite connector supports authenticating as a real user (via OAuth) only. It'd be better for us if we could use a Service User for this purpose as it lets us have finer grain control of permissions Fivetran needs (as I understand currently the integration requires admin-level access to function fully, we'd prefer grant read-only) - and in HiBob keeps Fivetran access managed in the same place as other API integrations we have, rather than mixed in with our staff accounts.
-
Official comment
Hi Daniel -
Thanks for submitting this feature request. Are you able to control the access with OAuth via the scopes provided by HiBob? Typically OAuth is the preferred and most secure authentication mechanism, and thus we opt for this when it's available.
Thanks,
Erin
-
Hi Erin, thanks for the reply.
I think I must have mixed up the setup process for another connector when I wrote about OAuth, looking at the setup guide (https://fivetran.com/docs/applications/hibob/setup-guide) has jogged my memory. Double-checked and I'm able to configure permissions in HiBob when creating the API token there.
Apologies for the confusion, I think this request is fine to close
-
Hi team,
I'm upvoting this request because for me it's essential that we can connect systems with pure service accounts, and not employee accounts. I'd say it's even an engineering best practice. Employee accounts can always give problems when the person faces any change in the company (department change, temporary or permanent leave for instance).
Service Accounts should be the standard way to authenticate for data transfer and I'm sure Fivetran Engineering understands this need. Please consider this again for implementation.
-
It would be great to have this feature.
-
Hi,
I am showing my support for the idea of having service accounts instead of using employee accounts.
Please sign in to leave a comment.
Comments
5 comments