Skip to main content

Attribute or template conflicts

Attribute or template conflicts can occur when Bravura Security Fabric or the Connector Pack is upgraded. During a Connector Pack upgrade, the installer runs loadplatform as a post-installation task to load connector-specific data (including attribute definitions) into the Bravura Security database. If the new attribute definitions differ from the existing ones, loadplatform reports a conflict.

A typical conflict warning looks like this:

Conflicting template(s) found for agtnt.exe. Please review the log, resolve any conflicts and then run "loadplatform -force -a agtnt.exe" to apply the changes.

The idmsuite.log file describes which attributes or templates are at fault and shows the proposed and existing values. For example:

attrdef = {
conflicts = {
accountNameHistory 632328ff-c281-41cb-9545-9e753dd4d48e = {
"proposed data" =
632328ff-c281-41cb-9545-9e753dd4d48e,accountNameHistory,0,AD,1,1,1,I,0,0,N,S,,0,-1,0,50,0,0;
"existing data" =
632328ff-c281-41cb-9545-9e753dd4d48e,accountNameHistory,0,AD,1,1,1,C,0,0,N,S,,0,-1,0,50,0,0;
};

In this example, the proposed data changes the attribute action from "C" (copy) to "I" (ignore). Forcing the update would revert the attribute to the default "ignore" action, which may break existing behavior that depends on the attribute value being copied.

Warning

Do not run loadplatform -force without first reviewing the conflicts. Bravura Security recommends keeping pre-existing attribute overrides unchanged in most cases. Forcing the default definitions can revert customized attribute actions and break PSLang scripts or automation that depend on those values.

It is the responsibility of the Bravura Security Fabric administrator to determine which portions of the Bravura Security Fabric instance may be affected by changes to default attribute values or characteristics; for example, the attribute's value may no longer be queried by default. If PSLang scripts make decisions based on this attribute's value, the decisions may no longer be correct.

Note

The Connector Pack upgrade process does not modify any existing attribute definitions used by the instance. You must decide which, if any, attributes should be modified when upgrading the Connector Pack.

If you choose to apply the update, back up the attrdef and attrdefval tables before updating the values. The attrdef and attrdefval CSV files are located in the agent\dat directory.

There are two ways to update the attribute default values:

  • Run loadplatform with the -force flag. This applies all changes for the connectors you specify. See the loadplatform usage information for details.

  • Override individual attributes from the Target system attributes page. You can override attributes at the target system or target system type level. See Account attributes in the Bravura Security Fabric documentation for details.

To forcibly update the attributes or templates, run loadplatform with the -force flag. For example:

loadplatform.exe -force -a <connector name>

To see a list of all loadplatform arguments, run:

loadplatform.exe --help

See usage information on loadplatform.

Note

In most Connector Pack upgrade scenarios, the conflict warnings can be safely ignored. The pre-existing attribute definitions remain in effect and the connectors operate with the existing configuration.

In this section: