# daloRADIUS operators handling change

May 9, 2010 ~ 1 min read

daloRADIUS operators handling change
====================================

*   [daloradius](https://lirantal.com/tag/daloradius)
*   [security](https://lirantal.com/tag/security)
*   [auth](https://lirantal.com/tag/auth)

share this story on

[](https://twitter.com/share?url=https://lirantal.com/blog/2010-05-09/&text=%22daloRADIUS%20operators%20handling%20change%22&via=liran_tal)[](https://www.facebook.com/sharer.php?u=https://lirantal.com/blog/2010-05-09/)[](https://www.linkedin.com/shareArticle?url=https://lirantal.com/blog/2010-05-09/&title=daloRADIUS%20operators%20handling%20change)[](https://wa.me/?text=daloRADIUS%20operators%20handling%20change%20https://lirantal.com/blog/2010-05-09/)

![RBAC, ACLs, operators, groups, and other access control related changes in daloRADIUS](https://cdn.hashnode.com/res/hashnode/image/upload/v1692641527986/61c921ed-55a7-40f5-922b-f4095576b379.jpeg)

We’ve introduced a change in the db schema to allow a more flexible management of the ACLs (access lists) an operator has.

The change has already been pushed into SVN a while back and requires to remove the current operators table and replace it with a new one and additional tables as well.

Here is how the new operators ACL page looks like:

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1692641531923/f5b1bdc2-7374-43cc-bae1-67d598db021b.png)