Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
tutorial:adm:roles_-_import_data_from_csv [2019/06/12 14:15] hanakp |
tutorial:adm:roles_-_import_data_from_csv [2019/07/11 11:48] doischert |
||
---|---|---|---|
Line 7: | Line 7: | ||
==== 1b. Prepare CSV file ==== | ==== 1b. Prepare CSV file ==== | ||
- | Here is an example of CSV file which can be used for import | + | Here is an example of CSV file which can be used for importing (or updating) |
< | < | ||
- | roles; | + | roles; |
- | Manager;Some role description | + | Manager-A;Leader; |
- | " | + | LAY-SP; |
- | PAY-OP | + | "CORE-CLOSE |
- | PAY-SP | + | AB-role";desc;attr1 |
- | PAY-BLL | + | |
- | AMT-BLK | + | |
- | ACC-CLOSE";Some roles description | + | |
</ | </ | ||
- | As you can see roles column can be single or multivalued. For multivalued roles, | + | As you can see roles column can contain |
- | CSV file can have optional number of columns, role and description columns | + | CSV file can have optional number of columns: column names are specified in setup of LRT. |
+ | |||
+ | The result of this LRT used with this CSV file should: | ||
+ | * 4 new roles (Manager-A, LAY-SP, CORE-CLOSE, AB-role) | ||
+ | * Manager-A will only have a description set (Leader) | ||
+ | * LAY-SP will have a description (Manager), attribute (attr1), criticality (3), guarantee by identity (with user-name " | ||
+ | * Roles CORE-CLOSE and AB-role will have a description (" | ||
==== Create new LongRunningTask ==== | ==== Create new LongRunningTask ==== | ||
- | Now we will create the new LongRunningTask(LRT). As shown in the picture, go to Settings → Task scheduler → Scheduled tasks and hit green " | + | Now we will create the new LongRunningTask (LRT). As shown in the picture, go to Settings → Task scheduler → Scheduled tasks and hit green " |
+ | |||
+ | {{ : | ||
==== Fill all attributes ==== | ==== Fill all attributes ==== | ||
Line 34: | Line 39: | ||
- Import csv file - dropzone to select or drop csv file | - Import csv file - dropzone to select or drop csv file | ||
- Column with roles - Name of the column with roles in csv file | - Column with roles - Name of the column with roles in csv file | ||
- | - Column with description - name of the column with role description, | + | - Column with description - name of the column with role description, |
- | - Column separator - separator of columns in csv file | + | - Column with attributes - name of the column with role attributes, can be also used to update attributes (if your CSV file doesn' |
- | - Multi value separator - ( Char, default: new line ) separator of multi valued role names in csv file, new line separator is default export from excel, but for better clarity of csv file, it's recommended to use some symbol instead | + | - Column with criticality - name of the column with role criticality, |
+ | - Column with guarantee - name of the column with role guarantee by identity login, can be also used to update guarantee (if your CSV file doesn' | ||
+ | - Column with guarantee role - name of the column with role guarantee by role code, can be also used to update role guarantee (if your CSV file doesn' | ||
+ | - Form definition code - the code for the definition which will contain the added attributes | ||
+ | - Column separator - separator of columns in csv file (default ; ) | ||
+ | - Multi value separator - (Char, default: new line) separator of multi valued role names in the csv file, new line separator is default export from excel, but for better clarity of the csv file, it's recommended to use some symbol instead | ||
- System name - name of the system to connect with roles | - System name - name of the system to connect with roles | ||
- | - MemberOf attribute name - ( default: rights ) - name of multi valued attribute for merge, attribute named " | + | - MemberOf attribute name - (default: rights) - name of multi valued attribute for merge, attribute named " |
- | - Can be requested - ( Boolean ) - Fills can be requested, can be also used to update already imported settings | + | - Can be requested - (Boolean) - Fills can be requested, can be also used to update already imported settings |
+ | |||
+ | <note important> | ||
+ | |||
+ | < | ||
+ | |||
+ | {{ : | ||
+ | {{ : | ||
- | {{: | ||
==== Run the task ==== | ==== Run the task ==== | ||
Line 48: | Line 64: | ||
{{: | {{: | ||
- | And we also need to process it in all tasks. | + | You can check the status of the created roles in the "all tasks" panel in the task detail. Here you can find information about roles created, updated, or already existing. |
- | + | ||
- | {{: | + | |
- | You can check status about created roles in "all tasks" panel in task detail. Here you can find information about created, updated or already existing | + | At this point, everything should be set up and when the task ends, roles are imported in IdM with their attributes, placed in the catalogue named by the system name. |
- | Everything should be set up so far and when the task ends, roles are imported in IdM, placed in catalogue named by system name. | + | {{ : |
==== Known issues ==== | ==== Known issues ==== |