oso
oso copied to clipboard
osohq
oso across multiple services
This is an external tracking issue to:
- Gauge interest from the community for this feature
- Learn about what you'd want to see out of it if we worked on it.
So please:
- Upvote the issue if it's important to you, and
- Comment with any relevant info on your requirements use cases, etc.
Thanks!
PS We do all our internal engineering issue tracking separately in Notion, so you won't necessarily see regular updates to the project status here even once we begin work.
Hi @gneray I might be interested in this since my use case would require using OSO in multiple services, but I am not sure I quite understand what you are thinking about implementing from the OSO side and I would appreciate a bit of elaboration.
The way I see it, OSO could be used as a library for a service that is a central authority for permissions or each service could have it's own OSO embedded. Are you thinking along the lines of supporting hybrid approach (as described in Architecture article in OSO Academy) and make external policy evaluation easier? This is something that sounds awesome and I would probably end up implementing it on my own if I make a decision to use OSO with a hybrid model.
Thanks.
Hi @delicb, yes, you've got the options more or less right. And yes, the hybrid model is at the top of the heap, though there are still a number of options we're considering.
If you are thinking about implementing something like this, how about we discuss it together and we can at a minimum advise you on it based on the work we've done thus far, and ideally collaborate on whatever goes into Oso?
@gneray That sounds great. I have not yet made a decision on the overall approach and architecture, but as of now all the options are open (centralized, decentralized, and hybrid architecture).
I would be happy to chat about the work you have you have done so far and what your thoughts are about the topic going forward.