Bug ID 693215: Creating custom Resource Groups

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IQ Platform(all modules)

Known Affected Versions:
5.4.0, 5.4.0 HF1, 5.4.0 HF2, 6.0.0, 6.0.1

Opened: Nov 07, 2017
Severity: 3-Major

Symptoms

If you are creating a custom resource group, you will need to make sure to include the "template" object in that group for certain kinds of objects (detailed below). This is because these objects can have device-specific instances which are referenced from this "template" object. For proper access, you need to select both the template object as well as any device-specific objects. In order to do this, you must select all the instances for the devices you want (the device column will be filled in with the device name) AND select the template instance. The template instance is the one object of that name with no device column filled in.

Impact

If you do not select the template object, then the role will not have proper permission to access the selected device instances. This will cause errors in virtually every workflow that uses the above object types detailed above.

Conditions

This is the case for these object types: LTM: Log Destinations - IPFIX Log Destinations - Remote High Speed Log Log Destinations - Management Port and, in general, all objects in Access Roles.

Workaround

The only issue is that this is not done automatically for custom roles. As long as the template object is selected, custom roles using the above mentioned objects will behave properly.

Fix Information

None

Behavior Change