5.4. Complete flow

This section provides an overview of the flows between the components in Nubus for Kubernetes, external directories, and third-party applications. The figures show the access relationships, small black dotted lines, and the flow relationships, bold dashed colorful lines. The focus of this section is on the flow relationships. The section uses the following structure:

• Level 1 - Breakdown on the functional component level

• Level 2 - Breakdown on the data object types between the functional components

This section considers the following object types:

• Directory objects

• UDM objects

• Event objects

See also

Directory objects in data objects section

for information about Directory objects.

UDM objects in data objects section

for information about UDM objects.

Event objects in data objects section

for information about Event objects.

5.4.1. Functional components level

This section describes the flow relationships on the functional component level for the object types Directory objects, UDM objects, and Event objects. You find the visualization in Fig. 5.13. The description order follows the creation process of the objects, starting with the Directory object, following with the UDM objects, and finally the Event objects.

Directory objects, orange line

• Flow from Identity Store and Directory Service to:

  • Directory Manager and back

  • Management UI and back

  • Provisioning Service

  • Portal Service

  • Third-party applications not part of Nubus for Kubernetes

  • Nubus Directory Importer

• Flow from External Directory service to Nubus Directory Importer.

UDM objects, blue line

• Flow from Management UI to Directory Manager and back.

• Flow from Nubus Directory Importer to Directory Manager.

• Flow from Directory Manager to:

  • Authorization Service

  • Portal Service

  • Third-party application not part of Nubus

  • Provisioning Service

Event objects, black line

• Flow from Provisioning Service to:

  • Consumer of Provisioning Service

  • Portal Service

  • End User Self Service

Fig. 5.13 ArchiMate flow relationships between functional components

To enlarge the figure, follow the tips in How to use the document.

5.4.2. Behavior level

This section describes the object flow relations on the functional level in Fig. 5.14. The structure of the section is identical to the previous section Functional components level.

Directory objects, orange line

• Flow from LDAP Server to:

  • UDM Library in Directory Manager

  • UDM Listener in Provisioning Service

  • Keycloak in Identity Provider

  • Portal Consumer in Portal Service

  • UMC Server in Management UI

  • Nubus Directory Importer

  • Third-party application not part of Nubus

• Flow to components in Identity Store and Directory Service:

  • From LDAP Primary to LDAP Server

  • From UMC Server to LDAP Primary

  • From UDM Library to LDAP Primary

• Flow from UDM Listener to UDM Transformer in Provisioning Service

UDM objects, blue line

• Flow from UMC Server to UDM Library

• Flow from UDM Library to:

  • UMC Server

  • UDM HTTP REST API and back

• Flow from UDM HTTP REST API to:

  • Portal Consumer in Portal Service

  • Guardian Authorization HTTP REST API in Authorization Service

  • Prefill Service in Provisioning Service

• Flow to UDM HTTP REST API from:

  • Nubus Directory Importer

  • Third-party application not part of Nubus

Event objects, black line

• Flow from UDM Transformer to Dispatcher

• Flow from Dispatcher to Events and Consumer API

• Flow from Events and Consumer API to:

  • Consumer of Provisioning Service

  • Portal Consumer

• Flow from Prefill Service to Events and Consumer API

Fig. 5.14 ArchiMate flow relationships on functional level

To enlarge the figure, follow the tips in How to use the document.