The first row in the entity file must be a header row. Each subsequent row represents a single user, where the row contains the following fields:
Note: The UniqueID, Endpoint Type, and Endpoint Name fields do not have to appear in the Users database file for the connector defined as "As Users". However, for flexibility reasons, we recommend including them. Any connector defined as "As Accounts" or "As Users and as Accounts" must include these three required fields.
The first row in the entity file must be a header row. Each subsequent row represents a single resource and contains the following fields, where a combination of Resource Name 1, 2, and 3 is the key and is assumed to be unique:
If you want to use custom role attributes, the first row in the entity file must be a header row. Otherwise, you can use the previous roles file format that did not require a header row.
The following system properties define how the file is treated:
Defines if the first line in the file is read as a header row. If this property is set to true, the product reads the first line as a header row. If this property is set to false, the product automatically detects if the first row is a header row, based on the value of the following property.
Default: False
Defines the field name to match to detect if the first line in the file is a header row when csvImport.roles.forceHeader.enable is set to false. When csvImport.roles.forceHeader.enable is set to true, this property is not used.
Default: rolename
The file has one row per role definition, each with the following fixed fields:
For custom role attributes, add them to the roles file after the Expiration Date field.
Copyright © 2014 CA.
All rights reserved.
|
|