Hey folks :wave:, <this issue is quite alarming to...
# connector-contributions
e
Hey folks 👋, this issue is quite alarming to us. It represents a very real chance for an inexperienced user to break a destination resulting in the need to trigger an enormous volume of historical resyncs. Can we please get some eyes on this or at least an idea of where this sits in the priorities? If RBAC existed for the OSS version we would be able to lock this down from our end but it doesn’t so we can’t
j
We were able to lock down Airbyte OSS pretty easily without RBAC capabilities in Airbyte
e
Oh really? We want our users to be able to create new sources and connections but not edit the destinations (and ideally nothing they did not create). How did you achieve this and what level of control did you manage to achieve?
j
So we don't do that level of granularity but you could create an RBAC layer in front of Airbyte using something like AWS Verified Permissions and Cedar or OPA. Not sure where you are running Airbyte. https://docs.aws.amazon.com/prescriptive-guidance/latest/saas-multitenant-api-access-authorization/avp-basic-abac-examples.html
So the API access model is outside of the Airbyte application in this case
We use an identity-based reverse proxy to control access to Airbyte, but not specific Airbyte API endpoints
e
Cool. I’d seen a POC article about this before. We want users to have self-service access but since the backend db doesn’t record who creates what and there’s no RBAC, we’re worried about users breaking things they don’t own. I’ll give this a look and see if we can take inspiration
j
Keep in mind that the Airbyte OSS license does not allow you to provide direct access to Airbyte to end-users as a managed service
That is why there is no native RBAC
e
Ah, I get what you mean. No this is our internal ingestion tool that we’re migrating to from Fivetran. We operate a self-serve model for our analysts but don’t want any eager beavers hitting the wrong button and ruining it for everyone else
j
Got it. We also moved from Fivetran to Airbyte
e
Thanks for all of this. They should still fix the issue that someone else opened. It just opens up every connection to being borked by accident, no matter how many people are accessing the UI
j
You're welcome. And I agree