Import an administrator
Administrators can be imported into the database from a .csv (comma separated value) file through the administrators view.
Create an import file
To import administrators, create a comma separated value (.csv) file using any text editor or spreadsheet tool. If you are using a text editor to create the file, use commas to separate the fields when you enter the data. Use carriage returns to separate records.
The first row in the file is a header row and must contain a comma separated list of the database field names that are included in the import file. The order of the fields does not matter. For example, to import administrators the header row could have the following fields: profileName,uid,authType,fn,ln
Unless otherwise specified, data type is a string with no size limitations. Fields are case sensitive. For example, if you have user IDs SMITH123 and Smith123, the database treats these as two separate user records. If you import something that already exists in the database, the existing record is updated with the new data from the import.
|
If you import an existing administrator, all fields will be replaced by those in the import file. |
|
|
When you select the Make Importable check box while exporting users, any user with an authentication type of "LDAP" is imported as a local user. |
Imported data is displayed on both the administrator user view and the user view. The table below lists all of the possible import data fields by the name that should be used in the header row, indicates which fields are required and provides a definition for each field.
Fields
|
Field |
Required |
Definition |
|---|---|---|
|
profileName |
Yes |
Admin Profile: Administrators must have an associated admin profile that provides them with permissions for features in FortiNAC. Enter the name of the admin profile that matches an existing profile in the database. |
|
uid |
Yes |
User ID: Unique alpha numeric user ID. If a directory is used for authentically the FortiNAC database is synchronized with the directory, data for users with matching IDs is overwritten with data from the directory. For example, if you import a user with ID AB118 named Ann Brown and the directory contains a record of AB118 as Andrew Bowman, then your database shows AB118 Andrew Bowman. |
|
authType |
|
Authentication method used for this administrator. Types include:
|
|
fn |
|
User's first name. |
|
ln |
|
User's last name. |
|
|
|
User's e-mail address. For multiple e-mail addresses, enter addresses separated by commas or semi-colons. Messages are sent to all e-mail addresses provided. |
|
addr |
|
User's mailing address. |
|
city |
|
User's city. |
|
st |
|
User's state. |
|
zip |
|
User's postal code. |
|
ph |
|
User's telephone number. |
|
title |
|
User's title. |
|
notes |
|
Notes about this user. |
|
expireDate |
|
Expiration Date: Date that the user is aged out of the database. Date format is MM/dd/yy HH:mm AM/PM Timezone or 04/07/10 08:11 AM EST. |
|
createDate |
|
Creation Date: Date that the user record was created. Date format is MM/dd/yy HH:mm AM/PM Timezone or 04/07/10 08:11 AM EST. |
|
smsNum |
|
Mobile Number: User's mobile phone number. This can be used to send SMS Messages based on events and alarms. |
|
smsPro |
|
Mobile Provider: The carrier or provider for the user's mobile phone. This must match the name of one of the providers in the Mobile Providers list in the database. See Mobile providers. |
Sample import file
Below is a sample .csv file for importing administrators. The profileName and uid fields are required.
profileName,uid,authType,fn,ln
Administrator,ajones111,LDAP,,Jones
Administrator,admin111,CM,Admin,User111
Conference Accounts,dpcuser,CM,Elaine,White
Conference Accounts,ajames,CM,james,james