search

apohl79 / audiogridder

DSP servers using general purpose computers and networks
https://audiogridder.com
MIT License
761 stars 79 forks source link

Feature Request - ACL Server #931

Open BungalowBill9 opened 2 years ago

BungalowBill9 commented 2 years ago

Ok, seeing that this an opensource project I was going to download the code and try this myself but I figured that it may be a useful feature for more than myself and who's not better to implement it than the developers... Alright so here's my dilemma... I have a multi-user setup which has multiple people reaching out to these servers at any given time, so to have a primary access control server up that all the clients reach out to which in turn queries the rest of the servers could solve afew problems for me in two primary ways: 1) Consolidation for maintenance reasons... It would be far easier to maintain my servers with updates if I could put all the plugins from the same manufacturer on the same box unto themselves, but then this makes actually using them a nightmare because intuitiveness would suggest that they be sorted by category (comps, eq's, reverbs, etc) so when you're selecting plugins for your project you only have to dig through a list of what you're actually looking for... And 2) Administration... A good majority of plugins are paid for by specific users whom may or may not just want to be sharing for free what cost them money, so username\password access so said access control server could parse the list of available plugins to only show those that said particular user may have access to.... I guess that this could probably be tied to a Radius server no? So using the AG client would function as such: User initiates AG plugin and logs in unless an auth token is already available due to their probably already being logged in to something, user picks an access server from the list if there are more than one available and is presented with a list of categories, user selects a category and is presented with a list of plugins available to them, user selects a plugin and the access server commands said AG server to load a module for said user and populate it with the chosen plugin which is in turn directed back at the client in the normal fashion... Is this outside the scope of where you were going with this and thus should I attempt this upgrade on my own, or should I just be patient and wait?

Thanks, Dan

apohl79 commented 2 years ago

Hey Dan,

tbh I have never considered this kind of functionality. Not saying that it will never be implemented, but it will likely take a while. Anyways, it seems like a good suggestion and will keep the feature request. Once starting with something like this would require some work in designing the role and permissioning model properly.

Cheers, Andreas

BungalowBill9 commented 2 years ago

Thanks for the reply Andreas... As for the control and access, check out an open project like CASBIN and CASDOOR (edit: Sorry for it's inclusion but CASDOOR may not be freely usable, I'm still researching it)... But as for the usefulness I believe such a solution would also bring an answer to those on here looking for the flexibility to say bypass plugins in their project without having the client disconnecting from the server as the ACL server would be acting as a network proxy to hold those connections open... Having an intermediate server may bring an answer to some other problems as well such as categorizing or even hosting the servers on a completely different network as the ACL would sort of act as a gateway in those respects... I'll keep on the problem myself and if I happen to achieve any success I'll be sure to pass that along...

Thanks, Dan

mistaox commented 3 months ago

Any update on this request?