1. Introduction of IdM MP version 4.3 into the Fortuna organization and technical upgrade to version 4.4.1 over time.
2. Integration to selected systems:

• RON (source HR system)
• SUCCESS FACTORS SHELDON (source HR system)
• AD (active directory)
• BETSYS/NAVIPRO
• JIRA connector for offline application management mode

3. Management of internal and external employees
4. Implementation of business processes in IdM (employee life cycle, AD pace roles auto assigment, emergency leave, role management, ownership continuity etc…)
5. Introduction of functions like email/SMS notifications, reporting, connection to customer monitoring tool via restAPI

Solution infrastructure

Solution architecture

Connected applications and short description

Applications integrated to IdM can be divided into source and target applications. The source systems are used for importing/exporting user data, while the target systems are controlled by the IdM application.

RON (source HR system)

• Customer’s original HR source system and loading user data and organizational structure for CZ organization/identity

Success Factor Sheldon (source HR system)

• Customer’s current HR source system and loading user data and organizational structure for CZ/POL/IND/HR organization/identity
• Integration via JSON/REST OData API of SF endpoint via a customized midPoint connector called “SuccessFactorsConnector”

AD (active directory)

• Connection via LDAP connector
• Integration and management of users, groups

BETSYS/NAVIPRO

• This target system is managed by a custom REST-like service that provides basic CRUD operations. Authentication is based on username and password, which are used to retrieve the JWT token. MidPoint uses a custom connector called BetsysConnector that handles all operations.
• There are several instances of BetsysConnector resources, each associated with a specific country. In addition, each country is associated with different environments such as PREMATCH, LIVE and IVG. For each country and environment combination, a unique resource instance is created that differs in connection configuration.
• The current solution is for the CZ country, with plans to integrate additional countries.

JIRA connector for offline application management mode

• Systems that are too small or impractical to integrate with IdM via the online connector are connected in “offline” mode. In this mode, IdM midPoint does not directly create and manage accounts on target systems via API calls.
• Instead, a so-called “Jira ticketing” system is used, while requiring manual admin work.
  SAP B1, IMS