Skip to end of metadata
Go to start of metadata

This is a description of the samples in:

https://github.com/Evolveum/midpoint/tree/master/samples/evolveum

Basic Idea

The demo shows a small organization using Evolveum team members as examples. The goal is to show midPoint features such as:

  • User management
  • Organziational structure
  • Role catalog
  • ...

Setup

Import all the XML files from the sample directory.

midPoint setup up:

  • Setup up user template in the system configuration
  • Setup up org template in the system configuration
  • Set up role catalog in system configuration (<roleManagement><roleCatalogRef oid="00000000-ee88-6666-0000-c00000000000"/></roleManagement>)

Resources

HR

CSV resource that contains simple employee data.

CSV file setup

Copy hr.csv file from samples/evolveum to midpoint.home/resources/

OpenLDAP

Target resource.

DN suffix: dc=evolveum,dc=net

OpenLDAP Setup

 

Users

usernamepassworddescription
administrator5ecr3tsuperuser
semancikqwe123manager of serveral orgs
role approver
   
   

 

Job Roles

There are several job roles that are automatically assigned: CEO, Software Developer, IDM Engineers, etc. These roles are automatically assigned in the user template based on the value of title property. This property is inbound mapped from the HR job attribute.

Organizational Structure

There is a functional organizational structure with divisions and departments. Some organizational units have managers (semancik, ifarinic; they have Manager role). The managers are delegated administrators and approvers. They can see people in their parts of organizational structure.

Functional organizational structure membership is automatically assigned in user template based on the value of organizationalUnit property. This is inbound mapped from HR orgId attribute.

There is also project organizational structure. But this not really used now.

Role Catalog

There is a simple role catalog with couple of applications. The roles in "Jira" application also have corresponding LDAP groups. The devel, admin ans write roles are subject to approval. The reader roles do not have approval. The aditor roles are not requestable at all.

roleapprover 
Jira Administratorsemancik 
   
   

 

 

  • No labels