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:report_compare_value_idm_to_system [2019/09/11 09:05] stloukalp |
tutorial:adm:report_compare_value_idm_to_system [2019/11/08 12:41] doischert |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Report - Compare values in IdM to system ====== | ====== Report - Compare values in IdM to system ====== | ||
- | This tutorial shows how to create a report for the chosen identities. | + | This tutorial shows how to create a report for the chosen identities |
- | Report | + | This report can be used if you change some attribute or in script where the value is calculated. |
- | This report can be used, if you will change some attribute or in script, where value is calculated. | + | |
===== Preparation ===== | ===== Preparation ===== | ||
- | * Report | + | * The report |
- | * Connected | + | * Have a connected |
===== Report ===== | ===== Report ===== | ||
Line 16: | Line 15: | ||
{{ : | {{ : | ||
* Select report ' | * Select report ' | ||
- | * And now we need **system** we want compare values with, it is select | + | * And now we need to select the **system** we want to compare |
- | * **Attributes** - we need identificators of mapped attributes separated by comma. | + | * **Attributes** - we need identificators of mapped attributes separated by a comma. |
- | * **Mapping** - we need ID of mapping, where theese | + | * **Mapping** - we need the ID of the mapping where these attributes are defined. |
* **Treenode** - you will select identities in this organization and identities in child organizations | * **Treenode** - you will select identities in this organization and identities in child organizations | ||
- | * **Identities** - fill identities or Treenode. Treenode will select | + | * **Identities** - select identities. There is a select box and it is convenient if you want a report for only a few identities. |
- | * These ID' | + | * These IDs can be found in tables with IdM in development stage or in Audit. But we will show you the easiest way to get those IDs. |
{{ : | {{ : | ||
- | * Click on tab **Systems** and select system | + | * Click on tab **Systems** and select |
{{ : | {{ : | ||
- | * Click on **Mapping** | + | * Click on tab **Mapping** |
- | * There are attributes mapping, | + | * You will see attributes mapping, there could be more than one, specifically for synchronization, |
- | * Click again on ' | + | * Click again on the ' |
{{ : | {{ : | ||
- | * Now you have open attribute mapping and in URL of your browser | + | * Now you have to open the attribute mapping and in the URL of your browser |
{{ : | {{ : | ||
- | * On lower part of this page there are your mapped attributes, select one and click again on ' | + | * In the lower part of this page you will see your mapped attributes, select one and click again on ' |
{{ : | {{ : | ||
- | * ID of this attribut is again in URL in your browser, copy it somewhere too. | + | * ID of this attribut is again in the URL in your browser, copy it somewhere too. |
+ | * You can copy more IDs of attributes from same mapping. | ||
{{ : | {{ : | ||
- | | + | * If you want get an ID of tree node, click on **Organization** and on the tab **Structure elements** click on the ' |
- | * Yeah we got one here, but we cannot directly use this script, because there can be used ' | + | |
- | * Copy that call of script ' | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | * Click on **Setting** and **Script definitions** and click on **Add** | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | * Past in call of that script, let it in Standard category. Write in description something like 'this script is used in report' | + | |
- | * Click on **Save and continue**. | + | |
- | * Now you can copy more ID's of attributes from that mapping. | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | | + | |
{{ : | {{ : | ||
- | * Again in URL there is ID of that organization node. | + | * Again in URL there is an ID of that organization node. |
{{ : | {{ : | ||
- | * Now we have all necessary | + | * Now we have all the necessary |
- | * Select System (the right one, which has the mapping we used) | + | * Select System (the one which has the mapping we used) |
- | * Write in ID' | + | * Write in IDs of attributes as in the picture bellow (seperated by comma) |
* Past Mapping ID | * Past Mapping ID | ||
- | * You can past tree node or as in our example select a fet identities. | + | * You can pass a tree node or as in our example select a few identities. |
* Click on **Generate report** | * Click on **Generate report** | ||
- | {{ : | + | {{ : |
- | * Now report is generating, it could take a few minutes, based on how many attributes and how many identities are selected. | + | * Now the report is generating, it could take a few minutes, based on how many attributes and how many identities are selected. |
- | * And then there is completed | + | * Once the report |
{{ : | {{ : | ||
- | * Example of report you can see bellow. | + | * You can see an example of the report |
- | * It shows status in first column, | + | * It shows status in first column, |
- | * Next are attributes we selected. | + | * Next are the attributes we selected. |
* For single value attributes: | * For single value attributes: | ||
- | * If value is blue, it means in system and in IdM it is same. | + | * If value is blue, **it means the value in the system and in IdM is the same**. |
- | * Otherwise it will write in green ' | + | * Otherwise it will write in green ' |
* Multivalued attributes are not supported yet, only multivalued attributes with merge strategy (it is often used with Active Directory system for provisioning of membership - ldapGroups) | * Multivalued attributes are not supported yet, only multivalued attributes with merge strategy (it is often used with Active Directory system for provisioning of membership - ldapGroups) | ||
- | * Blue values are same in IdM and in system | + | * Blue values are the values which are the same in IdM as in the system |
- | * Red values are missing in IdM and are in System | + | * Red values are values |
- | * Green values are in IdM and are missing in System | + | * Green values are the values which are present |
{{ : | {{ : | ||
- | Thank you for reading this tutorial and I hope this tutorial and report is useful | + | ====Override script==== |
+ | If you write a new script or want to change the current one, but you are in the production environment, | ||
+ | |||
+ | * Click on **Setting** and **Script definitions** and click on **Add** | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | * Here you need to call that new script, which will override the current one. You can generate it in the mapped attribute or copy existing the one and edit it. So write in the call for that new script. | ||
+ | * Leave it in Standard category. | ||
+ | * Write in description something like 'this script is used in report' | ||
+ | * Write the code and the script name. | ||
+ | * Click on **Save and continue**. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | * Again fill in System and mapping ID's | ||
+ | * Fill in attributes ID but after attribute ID which you want to override in the script, write colon and code of script like ID: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Thank you for reading this tutorial and I hope this tutorial and report is useful |