A user role that can do anything on the box, including full access to all objects in all partitions.
A user role that has limited read/write access, such as enabling/disabling nodes, pools, and members…., but not adding/removing nodes from pools.
A user role that read-only access.
A user role who can read/write every configuration aspect in ASM, read/write to all applications, and deal with all configuration that is global per ASM.
An uninitialized or invalid role.
A user role who can administer all objects in a specific partition, including read access in the Common partition, but no objects outside of his/her partition.
A user role who can only modify objects in a specific partition (i.e. not create or delete)
A user role who can administer objects for an application (LTM, GTM, LC…). This includes ability to read/update permissions to pools, nodes, monitors, add/remove members from pools…
A user role who can administer all security keys and certificates in a partition.
A user role who can manage user accounts in a partition.
A user role who can manage everything except user accounts and device authentication settings
A user role who has read/write rights to perform changes on ASM policies within one or many web application or one or many administrative domain partitions.
A user who has certain privileges on the Enterprise Management server.
The links to the sample code below are remnants of the old DevCentral wiki and will result in a 404 error. For best results, please copy the link text and search the codeshare directly on DevCentral.
The BIG-IP API Reference documentation contains community-contributed content. F5 does not monitor or control community code contributions. We make no guarantees or warranties regarding the available code, and it may contain errors, defects, bugs, inaccuracies, or security vulnerabilities. Your access to and use of any code available in the BIG-IP API reference guides is solely at your own risk.