This page will walk through the process of setting up user profiles in bulk via a file upload.
This process is currently under review for improvements (moving to a UI based upload / bulk action). Your feedback is greatly appreciated.
Upload File Format
Ensure the file you create follows the following format
|
Property |
Value |
|---|---|
|
Encoding |
UTF-8 (No BOM) |
|
File Delimiter |
| (pipe) |
|
Headers |
Ordered and present as per contract all in uppercase. |
|
Record Quoting |
All fields enclosed in double quotes. "value". Any double quotes inside the field value must be escaped with an additional double quote. |
|
Record Delimiter |
\ |
|
(new line character) |
|
|
Empty Fields |
Non mandatory fields may be left empty. Note that an empty field must still be doubled quoted. |
Step 1) Generate user upload file
-
Create a csv file with the following parameters:
-
Extract contains a row per user.
-
File name: USERS_YYYYMMDDHHMMSS.csv
-
Daily Load: Extracts new users.
-
Historical Load: Full snapshot of users.
-
Follows the file format above.
-
|
Column |
Data Type |
Value Mandatory |
Description |
|---|---|---|---|
|
USERNAME |
STRING |
Y |
Unique id for the user. Typically email of the user especially if SSO with Active Directory is used. |
|
FIRST_NAME |
STRING |
Y if IS_LOGIN_USER = 'Y' |
Example: Jane |
|
LAST_NAME |
STRING |
Y if IS_LOGIN_USER = 'Y' |
Example: Doe |
|
|
STRING |
Y if IS_LOGIN_USER = 'Y' |
Example: Jane.Doe@email.com |
|
DESCRIPTION |
STRING |
N |
Description or Title of the user |
|
IS_SYSTEM_USER |
STRING |
N |
Is the user a human user or a system account? One of: (Y, N) |
|
IS_LOGIN_USER |
STRING |
N |
Will the user log into KADA? One of: (Y, N). Default to 'N' if not provided |
|
ROLES |
STRING |
N |
Comma separated string of roles. Defaults to "kada_user" if no role is provided. Valid values: kada_user, kada_admin, kada_data_manager, kada_business_user, kada_data_gov_user |
|
GROUP_NAME |
STRING |
N |
The group (Team) the user belongs to. Must match a value from GROUP MAPPING interface |
|
USER_ID |
STRING |
N |
INTERNAL use only. Leave empty |
Step 2) Generate Team upload file
-
Create a csv file using AD / LDAP with the following parameters:
-
Extract contains a row per group.
-
File name: GROUPS_YYYYMMDDHHMMSS.csv
-
Daily Load: Extracts new groups.
-
Historical Load: Full snapshot of groups.
-
In this context Groups = Teams
|
Column |
Data Type |
Value Mandatory |
Description |
|---|---|---|---|
|
NAME |
STRING |
Y |
Name of group (i.e. Team). Must be unique. |
|
PARENT_NAME |
STRING |
N |
Name of the parent team. Must match the team name in another row |
|
DESCRIPTION |
STRING |
N |
Description of the team for presentation within the K application |
Step 3) Upload user and group files to K
Requires K administrator access and access to your K instance storage container.
-
Log into K
-
Go to Platform Settings → Sources
-
Click Add Source.
-
Select MICROSOFT_WINDOW_AD or LDAP.
-
Select Load from File
-
Add a Name: e.g. Active Directory
-
Add a Host: e.g. ActiveDirectory
-
Note down the landing folder e.g. windows_ad
-
Click Next and Finalise the setup
-
-
Access the folder created via Azure Storage Explorer and the SAS token provided by K (for SaaS) or the storage container for your Cloud implementation
-
Upload the files above to the landing directory for the source you created e.g. kada-data/lz/windows_ad/landing
-
Go back to the Sources page. Click run manual load action on the source you created
-
Check the monitor page for the status of the job. On completion, your new teams and users will have been created