It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda CloudGen Firewall

How to Allow Administrators with a Limited Scope to Use Pool Licenses

  • Last updated on

Previously, pool licenses could be managed only on a global level in a Control Center. As of firmware release 9.0.1, pool licenses can be configured so that administrators are allowed to handle them on a range/cluster level.

When you are already using pool licenses and you have configured admins for specific ranges and clusters, upgrading a Control Center to 9.0.1 will have the effect, that all pool licenses will get the scope 'NONE', and only global administrators will be able to view the pool licenses!

Before You Begin

Ensure you have read the following articles:

These two articles explain all the necessary steps for a correct configuration.

This article explains the logic of how a matching between an administrative scope and a list of possible ranges/clusters can be achieved so that a CC administrator with a limited scope is allowed to administer certain pool licenses. It also assumes that there are already pool licenses present in your Control Center and that you have already configured administrators on your Control Center that you can manage at CONFIGURATION > ADMINS.

How Certain Control Center Administrators with a Limited Scope Are Allowed to Administer Pool Licenses

The Control Center is designed to be managed by an administrator with global permissions. However, as the configuration tree grows with larger and larger environments, maintenance tasks also become increasingly challenging, thus requiring the tasks to be distributed among additional administrators. These administrators must be configured in the Control Center at ADMINS. In the corresponding configuration view, you can also set the scope of the administrator's role in terms of a specific range and cluster.

administrative_scope.png

The list of administrators can be viewed in the Control Center at ADMINS:

cc_list_of_CC_admins.png

To keep the configuration manageable, the Control Center allows you to arrange the configuration tree for the managed appliances into subordinated segments, where each segment represents a range, which, in turn, can be segmented into clusters that ultimately contain the configurations for the managed boxes.

As a result, the permission to manage specific pool licenses with a limited scope depends on matching the administrator's scope to an identical set of values that the global administrator can configure. The Control Center extracts these values from the range/cluster structure of the configuration tree:

Relevant Nodes in the CC Configuration Tree

Matching Filter Extracted from Range/Cluster Structure of the Configuration Tree

CC_config_tree_with_ranges_clusters.png

CC_matching_range_cluster_filter.png

Example: The table above on the right shows the list that contains all valid filters for selecting which pool licenses may be managed by a specific administrator at CONFIGURATION > Configuration Tree > Multi Range > Global Settings > Pool Licenses:

CC_select_range_cluster_for_pool_licenses.png

A valid configuration in the Control Center could look like this:

List of Pool LicensesList of CC Admins

CC_pool_licenses_assigned_to_range_cluster.png

CC_admins_shortened_list_01.png

If a range-/cluster-related entry in the pop-up menu list matches any value of the column in the list of Control Center Admins, the associated administrator will be allowed to manage the related pool licenses.

As a result, the following administrators will be allowed to manage pool licenses for the following ranges/clusters. Note that an administrator is generally allowed to administer all ranges/clusters unless such permissions have been explicitly restricted, e.g., with a configuration level of 99, which refers to "read-only":

AdministratorPool LicenseAssociative Range/Cluster
GlobalBaseRange 3 / Cluster1
Global, r2c3adminAdvanced Threat ProtectionRange 2 / Cluster3
GlobalEnergize UpdatesRange 1 / Cluster83
c1admin, glinked1, ladmin1, ladmin2, rlinked, rlinked1BaseRange 1 / Cluster1
c2admin, rlinkedEnergize UpdatesRange 1 / Cluster2