Introduction
Entities basics
Entity queries
Linking entities
Filters
Entities in Result Table attributes
Postprocessing
Complex linkages and postprocessing
Hello there! In this video, you will learn about entities in ACDI reports, what they mean, how to create reports with entities, as well as how to manage entity filters and display attributes of secondary entities in final reports.
If you need a report that will display values for different objects linked with each other by an attribute like groups and its members, roles and users, role requests, approvers, requester, request, target user, etc., you must add a secondary entity or entities to a report.
Let's create a report that will show you data about all roles assigned to a user. This report will be created based on data from the snapshot. In ACDI there is a default Users Report which has only one entity, namely, a user from snapshot.
There are also some filters for this user, and the report displays a list of attributes in the Result Table.
Here is what you need to do: first, create a secondary entity—Role—and link it with the existing one. For this, go to Report Editor, choose a report that you want to use as a template,
click “Save as” and give it a new name. Now save.
Your custom report will appear on the reports list.
You may want to update some tags to use them later for placing the report in an appropriate submenu.
Let’s go back to an entity. Here you see that the base entity snapshot has a query “objectClass:inetOrgPerson.” This means that this entity will display information only about users from a snapshot.
Indices with the prefix report contain data from snapshots.
Okay, let's copy this entity and update the copy with customized properties.
Let’s change the query. You know that roles have the class “nrfRole.”
The entry in the “DateTime” field remains the same as for the copied entity, as do the entries in the “Entity Index” and “Entity primary key” fields.
The next step is to create a link between the two entities.
Roles are linked to users via different attributes. “nrfassignedroles” is an attribute that shows direct role assignments.
And the “nrfmemberof” attribute contains DN of roles assigned via different ways even using a nested child role assignment. Let's use the “nrfmemberof” attribute.
As you can see here, it contains a strict DN.
This means that for the entity “Role” you need to use DN for the “Source Attribute.”
Here “term” must be selected because it's a strict DN.
OK, you don't need any post-processing and want to link the “Role” to an entity “Snapshot.”
Snapshot’s attribute is “nrfMemberOf.”
One user may have many memberships as you can see in this example.
So, you linked entities from one side and now let's do it from the side of the primary entity.
The ”Source Attribute” here is “nrfMemberOf.” “Destination Entity name” – Role, “Destination Attribute” - DN.
Select here “many” to “one.” Let's save the settings.
Should you have any questions or require any assistance, please do not hesitate to contact us at any time swsupport.skypro@skypro.ch