If you have user and group data you want to manage in EmpowerID, but that data is in an application that is not connected to EmpowerID—and for which you do not want to create a connector—you can do so by creating a "tracking-only" account store to represent that application in EmpowerID and then import the data from that application to the tracking-only account store in delimited flat file format.
EmpowerID provides three workflows for each aspect of this type of situation.
When initiated, each of these workflows reads the flat file you upload and pulls from that file the necessary information to create the corresponding objects and object relationships in EmpowerID, adding those objects (user accounts and groups) and relationships (group membership) to the specified account store if they don't already exist in the account store. If EmpowerID finds that the account store already has an account or a group or a group membership that matches one or more records in the flat file, it ignores that particular record or records. This ensures that duplicate accounts, groups and group memberships are not created.
Once the user and group data has been added to the account store you create for the application, you can manage and audit it as you would any other type of user and group information. The only difference is that changes you make to those accounts and groups in EmpowerID are not reflected in the source application. Thus, to keep data changes in sync, any changes you make in EmpowerID need to be made in the application. |
This topic demonstrates how to import users and groups from file to EmpowerID.
1. Create a "tracking-only" account store in EmpowerID for the application containing the user and group data.
2. Have the user and group data you want to import in three separate delimited files:
Each file must have a certain number of fields that correspond to the EmpowerID object you are creating. These fields, listed by EmpowerID object type, are as follows: User Account: Name, Logon Name, Friendly Name Group: Name, Logon Name, Friendly Name Group Membership: Account Logon Name, Group Logon Name These fields do not have to be named as such in the flat file. They must, however, be able to map to those fields in EmpowerID. Besides these fields, the flat files can have any number of additional fields. If a corresponding field exists in EmpowerID, map them when importing. If the fields do not have a corresponding field in EmpowerID, ignore them. This is all demonstrated below. |
Click Import Users From CSV.
This initiates the Create Accounts From File workflow.
The field headers for this information in the flat file can be named anything, as long as you map them to the corresponding fields in EmpowerID. |
Map each of the required fields from the imported data to the appropriate EmpowerID account field. To do so, type the name of the required field in the drop-down below your related headers and then click the field to select it. For accounts, these fields are Name, LogonName, and FriendlyName.
In our example, we have imported data with the account logon name listed under the Logon header. As this header does not match the Logon Name field for the component in EmpowerID, we need to map it before submitting the workflow.
If the column headers in your flat file already match the required fields, you do not need to map them as the workflow does it for you. Additionally, if a field in the flat file does not have a corresponding account field in EmpowerID, the workflow ignores them. |
As needed, map all other fields to their corresponding EmpowerID fields.
If the column headers in your flat file already match the required fields, you do not need to map them as the workflow does it for you. Additionally, if a field in the flat file does not have a corresponding group field in EmpowerID, the workflow ignores them |
Map each of the required fields from the imported data to the appropriate EmpowerID account field. To do so, type the name of the required field in the drop-down and then click the field to select it. For group memberships, these fields are Account_LogonName for the user account, and Group_LogonName for the group.
In our example, we have imported data with the account logon name listed under the Account header and the group logon name under the Group header. As these headers do not match the required fields, we need to map them before submitting the workflow.
If the column headers in your flat file already match the required fields, you do not need to map them as the workflow does it for you. |
Once you have completed your mapping, click Submit.
|
|