Spudinski Posted September 22, 2012 Posted September 22, 2012 (edited) I'm currently busy thinking of ways to amend an access control system to the engine. But, I'm at a cross-road as to which approach will be best. The thing is, there's no need to make it over-complicated - but on the same point, it does need to be scalable. I was thinking of a Role-based Access Control system, NIST has a pretty good standardization for it here. From that article, I really like the Flat RBAC as it's simple, yet it can be improved on demand. I've drawn up a simple diagram of how it would work: The database isn't mapped here, but that should be the "simple" part of it all. Does anyone have any suggestions/comment for[/on] this? Edited October 17, 2012 by Spudinski Quote
Aventro Posted October 17, 2012 Posted October 17, 2012 The picture (?) of the diagram doesn't display. Quote
Spudinski Posted October 17, 2012 Author Posted October 17, 2012 The picture (?) of the diagram doesn't display. Updated original post. Quote
Aventro Posted October 17, 2012 Posted October 17, 2012 Yes, that would make sense to integrate. It's something similiar like Drupal, right? However, I believe it would be a efficient and easy approach and if well integrated could be a really great feature. Quote
Aventro Posted February 28, 2013 Posted February 28, 2013 You should enable overriding permissions as well as disabling certain permissions. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.