File Access Manager Attributes/Configuration

Schemas are defined on the Configuration tab. If an alert schema is defined, this will include the configuration needed to set up the Alerts. If the Unstructured schema is defined, this will include the configuration needed to set up the Target/Target Permissions.

  • Database URL - The jdbc connection URL for the File Access Manager database.

  • Driver Class - The SQLServer JDBC Driver class to use for the connection. This should be the appropriate jar for the version of SQLServer you are using with File Access Manager. It must be contained in the corresponding jdbc SQLServer jar file, and located in your IdentityIQ installation's \lib directory.

  • UserName - The database user name

  • Password - Password for the configured user name

  • Schema - Schema used for the File Access Manager database.

Referenced Applications

This is a list of applications to which the given permission are correlated. The target permissions are correlated to either a Link or ManagedAttribute belonging to one of the applications in the list.

Aggregate Inherited

True to aggregate inherited permissions. If set to true, the dataset will be much larger. If false, only the top level permissions are aggregated, and inheritance is assumed as defined on the native source.

Target Hosts

The File Access Manager Business Application Monitors (BAMs) from which to aggregate permissions.

Target Host Paths

This is a CSV of paths from which to aggregate. This aggregation starts at the given root paths, and discovers all permissions under these paths. If not specified, all target/target permissions for the specified BAM are aggregated.

The rules tab within the Application Definition user interface enables the defining of rules for given object types. The Application level rules and schema level rules, for schemas that allow them, are shown with the ability to select/edit (based off of correct capabilities) the given rules. The unstructured schema support Correlation/Creation/Customization/Refresh rules on the schema level.

Creation rules for unstructured schema will be of Rule Type TargetCreation

Refresh rules for unstructured schema will be of Rule Type TargetRefresh

Correlation rules for unstructured schema will be of Rule Type TargetCorrelation

Note: Customization rules might run multiple times, updating the same ResourceObject. For example, once for the provisioning result, once for the result in the provisioning plan, and once for the result in the account request.

Customization rules for unstructured schema will be of Rule Type ResourceObjectCustomization

The unstructured/associations schema AttributeDefinitions are used to define the columns to include in the query.