<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.czechidm.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://wiki.czechidm.com/feed.php">
        <title>IdStory Identity Manager</title>
        <description></description>
        <link>https://wiki.czechidm.com/</link>
        <image rdf:resource="https://wiki.czechidm.com/_media/wiki/logo.png" />
       <dc:date>2026-06-11T08:51:23+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://wiki.czechidm.com/devel/documentation/systems/dev/system-mapping?rev=1780560954&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.czechidm.com/devel/documentation/architecture/dev/backend?rev=1558937982&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.czechidm.com/devel/documentation/application_configuration/dev/backend?rev=1780993423&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.czechidm.com/devel/documentation/adm/configuration/events?rev=1557737394&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.czechidm.com/devel/documentation/architecture/dev/events?rev=1628839122&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.czechidm.com/devel/documentation/universal_requests?rev=1551284018&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.czechidm.com/devel/documentation/adm/systems/winrm_ad_connector?rev=1756717558&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.czechidm.com/devel/documentation/quickstart/dev/frontend?rev=1543388426&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.czechidm.com/devel/documentation/synchronization/dev/synchronization?rev=1714644276&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.czechidm.com/devel/documentation/identities/dev/contractual-relationship?rev=1550048080&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.czechidm.com/devel/documentation/requests/adm/universal_agenda?rev=1550152334&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://wiki.czechidm.com/_media/wiki/logo.png">
        <title>IdStory Identity Manager</title>
        <link>https://wiki.czechidm.com/</link>
        <url>https://wiki.czechidm.com/_media/wiki/logo.png</url>
    </image>
    <item rdf:about="https://wiki.czechidm.com/devel/documentation/systems/dev/system-mapping?rev=1780560954&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-06-04T08:15:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Connector configuration and attribute mapping</title>
        <link>https://wiki.czechidm.com/devel/documentation/systems/dev/system-mapping?rev=1780560954&amp;do=diff</link>
        <description>Connector configuration and attribute mapping

connector mapping system configuration merge authoritative skip excluded

Connector configuration

connector configuration

Creation of a newly connected system will be demonstrated on a database connector (ConnIdDBBundle). Firstly, we will create a new system named Table and choose the database connector. All settings for this connector are available in the</description>
    </item>
    <item rdf:about="https://wiki.czechidm.com/devel/documentation/architecture/dev/backend?rev=1558937982&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-05-27T06:19:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Architecture - backend</title>
        <link>https://wiki.czechidm.com/devel/documentation/architecture/dev/backend?rev=1558937982&amp;do=diff</link>
        <description>Architecture - backend

backend architecture



Backend is based primarily on the Spring and Activiti workflow technologies.

Application layers

Going from the bottom:

Entity (AbstractEntity ⇒ repository (AbstractEntityRepository) ⇒ dto (AbstractDto) ⇒ service (AbstractReadWriteDtoService</description>
    </item>
    <item rdf:about="https://wiki.czechidm.com/devel/documentation/application_configuration/dev/backend?rev=1780993423&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-06-09T08:23:43+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configuration - backend</title>
        <link>https://wiki.czechidm.com/devel/documentation/application_configuration/dev/backend?rev=1780993423&amp;do=diff</link>
        <description>Configuration - backend

configuration final property properties config setup

The application uses a Spring boot configuration in the application.properties files. All the configuration items which are used solely for idm begin with idm. prefix. The configuration items from the file can be overloaded through a setting agenda in the gui ⇒ a server restart isn't needed for changing the configuration with</description>
    </item>
    <item rdf:about="https://wiki.czechidm.com/devel/documentation/adm/configuration/events?rev=1557737394&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-05-13T08:49:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Events - processing of events</title>
        <link>https://wiki.czechidm.com/devel/documentation/adm/configuration/events?rev=1557737394&amp;do=diff</link>
        <description>Events - processing of events

An event mechanism has been designed to make extending and overlapping of the CzechIdM core functionality within any module possible.

The event (EntityEvent) with type (EventType) is published via EntityEventManager from different places in the application (</description>
    </item>
    <item rdf:about="https://wiki.czechidm.com/devel/documentation/architecture/dev/events?rev=1628839122&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-08-13T07:18:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Events - processing of events</title>
        <link>https://wiki.czechidm.com/devel/documentation/architecture/dev/events?rev=1628839122&amp;do=diff</link>
        <description>Events - processing of events

event architecture configuration processor

An event mechanism has been designed to make extending and overlapping of the CzechIdM core functionality within any module possible.

The event (EntityEvent) with type (EventType) is published via EntityEventManager from different places in the application (</description>
    </item>
    <item rdf:about="https://wiki.czechidm.com/devel/documentation/universal_requests?rev=1551284018&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-02-27T16:13:38+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Agenda of universal requests</title>
        <link>https://wiki.czechidm.com/devel/documentation/universal_requests?rev=1551284018&amp;do=diff</link>
        <description>Approval of role assignment Documentation Attributes of role
Agenda of universal requests

universal request

What is a universal request?

The universal request agenda allows you to create a request for any (supported) object in the IdM. A advantage versus the previous agendas for dealing with requests is versatility when there is no need to create a separate agenda for each additional approved object (such as the agenda for automatic roles requests and the agenda of requests for change a permi…</description>
    </item>
    <item rdf:about="https://wiki.czechidm.com/devel/documentation/adm/systems/winrm_ad_connector?rev=1756717558&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-09-01T09:05:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>WinRM + AD Connector</title>
        <link>https://wiki.czechidm.com/devel/documentation/adm/systems/winrm_ad_connector?rev=1756717558&amp;do=diff</link>
        <description>WinRM + AD Connector

This connector is combining WinRM and AD connector into one. The main advantage of this is you can execute operation by AD connector or by WinRM connector or with both together in specified order.

General information

Typical use cases for this combined connector are:</description>
    </item>
    <item rdf:about="https://wiki.czechidm.com/devel/documentation/quickstart/dev/frontend?rev=1543388426&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-11-28T07:00:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Quickstart - frontend</title>
        <link>https://wiki.czechidm.com/devel/documentation/quickstart/dev/frontend?rev=1543388426&amp;do=diff</link>
        <description>Quickstart - frontend

Frontend module is single npm packace with standard package.json descriptor and CzechIdM module descriptor:

package.json


{
  &quot;name&quot;: &quot;czechidm-example&quot;,
  &quot;version&quot;: &quot;7.3.0&quot;,
  &quot;description&quot;: &quot;Example module for CzechIdM devstack. This module can be duplicated and rename for create new optional CzechIdM module.&quot;,
  &quot;main&quot;: &quot;index.js&quot;,
  &quot;scripts&quot;: {
    &quot;test&quot;: &quot;echo \&quot;Error: no test specified\&quot; &amp;&amp; exit 1&quot;
  },
  &quot;keywords&quot;: [
    &quot;CzechIdM&quot;,
    &quot;example&quot;,
    &quot;IdM&quot;
  …</description>
    </item>
    <item rdf:about="https://wiki.czechidm.com/devel/documentation/synchronization/dev/synchronization?rev=1714644276&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-02T10:04:36+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Synchronization (of identities)</title>
        <link>https://wiki.czechidm.com/devel/documentation/synchronization/dev/synchronization?rev=1714644276&amp;do=diff</link>
        <description>Synchronization (of identities)

sync identity

The basic task of the synchronization is to ensure the correct state of the data on the end system and in IdM. Typically users´ accounts are considered as data. The correct state is defined both by the data in IdM (account management) and by the IdM configuration itself - usually by setting provisioning and synchronization on a given system.</description>
    </item>
    <item rdf:about="https://wiki.czechidm.com/devel/documentation/identities/dev/contractual-relationship?rev=1550048080&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-02-13T08:54:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Contractual relationship (CR)</title>
        <link>https://wiki.czechidm.com/devel/documentation/identities/dev/contractual-relationship?rev=1550048080&amp;do=diff</link>
        <description>Contractual relationship (CR)

contract identity

They define the link between the identity and the tree structure. In the application, we advance the logic according to which every identity has at least one CR. This is why there is one CR which is formed automatically to every identity after its creation according to the</description>
    </item>
    <item rdf:about="https://wiki.czechidm.com/devel/documentation/requests/adm/universal_agenda?rev=1550152334&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2019-02-14T13:52:14+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Agenda of universal requests</title>
        <link>https://wiki.czechidm.com/devel/documentation/requests/adm/universal_agenda?rev=1550152334&amp;do=diff</link>
        <description>Agenda of universal requests

universal request

What is a universal request?

The universal request agenda allows you to create a request for any (supported) object in IDM. One advantage in comparison with the previous agendas for dealing with requests is its versatility, as there is no need to create a separate agenda for each additional approved object (such as the agenda for automatic roles requests and the agenda of requests for changing permissions).</description>
    </item>
</rdf:RDF>
