|Applies To||RSA Product Set: Archer|
RSA Product/Service Type: RSA Archer (On-Premise)
RSA Version/Condition: 6.2 P2 HF1, 6.2 P3, 6.2 P4, 6.2 P5, 6.2 P6, 6.2 P7, 6.2 P8, 6.3 P1 HF1 and 6.3 P2
|Issue||How to update or import Users into the Record Permission Field.|
|Tasks||The Purpose of this Article is to explain how to update or import Users into the Record Permission Field using the File Transporter Data Feed. This Article covers importing both the LDAP users and as well as Non-LDAP users (local Archer users).|
|Resolution||Step 1: Identify the Key Field Definition for the File Transporter Data Feed|
In the Archer File Transporter Data Feed, it is best to have one field referenced as the Key Field Definition as referencing multiple fields can impact Application performance (one Key Field Definition per application is recommended for fast Data Feeds).
We want to make certain that there is at least one piece of unique data for each record can be leveraged for uniqueness.
Examples: TrackID, e-mail address or employee ID which may look like 12345, "email@example.com" or "Archer\Jamest"
Step 2: Configuring the format for the Username in the CSV file.
LDAP users in Archer should have this format Domain\UserName and non LDAP users will not include a domain. Using the correct format ensures your Data Feed is populated the Record Permission field(s) correctly. In the CSV file, you can have the following formats for the Record Permission field:
|Notes||- Each Username must be unique. While you can have two users with the same FirstName and LastName they can't have the same Username.|
- If you use the Username without Domain Name (method 2 from above), you must tick the "Default LDAP Configuration" in Archer under Access Control > LDAP Configuration > General tab otherwise you will receive the following error for every line in CSV during run the Data Feed: "The value in field 'Column01' cannot be converted, the item will be dropped". You refer to KB 000035879.
- Imported users need to have sufficient permission to the application.