I am an application developer, trying to create remote requests to update BIG-IP. Recently, I realize that iControl requires a full read and write access priviledged account access to BIG-IP v4.2. My IT management values the benefits of iControl in automating update of BIG-IP, but they would like to have additional ACL tagged on the interface method I could use. How can iControl interface methods be regulated via ACL? Any suggestion on design is greatly appreciated.
We are always looking at how we can enhance security and welcome any specific requests for features.
In 9.x, our authorization access check has been reworked to use a combination of the user's role and what method is being invoked.