5.2. UDM objects flow

This section gives an overview about the data flow of UDM objects. Write operation describes the features of the writing process.

See also

UDM objects

for information about UDM objects.

5.2.1. UDM objects processing flow

Fig. 5.5 shows the consumers of UDM objects in Nubus for Kubernetes on the functional component level.

1. Management UI

2. Directory Manager

3. Authorization Service

4. Provisioning Service

UDM objects relate to Directory objects that the UDM Library converts to and from. The following contexts make use of UDM objects:

1. The UDM Library in the Directory Manager converts Directory objects into UDM objects.

2. The UMC Server and the UDM HTTP REST API process UDM objects.

3. Other applications use the UDM HTTP REST API to access UDM objects.

Fig. 5.5 Components that consume UDM objects

To describe the data flow, differentiate between read and write operations for UDM objects. Fig. 5.5 and Fig. 5.6 show the read operations. The latter also shows the functions in each component.

For UDM objects, the journey starts with directory objects, their transformation to UDM objects, and the application of business logic in the UDM Library. The UMC Server and the UDM Transformer include the code of the UDM Library, thus each use the same logic on UDM objects.

The following components retrieve UDM objects from CRUD operations for UDM objects:

• Populate initial data for each consumer in the Prefill Service

• Retrieve attributes of actor and target in the Guardian Authorization HTTP REST API

• Write Portal configuration in the Portal Consumer

• Read dynamic portal assets, store for delivery for the portal assets in the Portal Frontend

The figure shows the data flow starting with the Directory objects. It also shows which function reads UDM objects and how they flow within Nubus.

Fig. 5.6 Functions that consume UDM objects

See also

Portal Service in the components section

for information about the functions of the component.

Management UI in the overview section

for information about the functions of the component.

Directory Manager in the components section

for information about the functions of the component.

Provisioning Service in the components section

for information about the functions of the service.

Authorization Service in the components section

for information about the functions of the service.

5.2.2. Write operation

Nubus for Kubernetes uses UDM objects as input for Directory objects. It only supports the UDM HTTP REST API in the Directory Manager to write data to the directory service, because the Directory Manager applies business logic before writing to the Directory Service.

Fig. 5.7 shows data flows for writing UDM objects that finally result in writing Directory objects. The central gatekeeper is the UDM Library. The UMC Server and the UDM HTTP REST API both use the UDM Library to create UDM objects.

The components Stack Data and Nubus Directory Importer both use the UDM HTTP REST API for their write operations, as well as, Third-party applications not part of Nubus.

Fig. 5.7 Data flow for creating UDM objects between components

Fig. 5.8 shows the detailed data flow for creating UDM objects. The following examples show which component creates UDM objects through which component:

• The Stack Data component loads initial data for the operation of Nubus into the Identity Store and Directory Service.

• The UMC Server converts UDM objects to Directory objects and writes them to the Identity Store and Directory Service through the UDM Library.

• The Nubus Directory Importer uses the UDM HTTP REST API in the Directory Manager to import data for the directory service.

• Third-party application, not part of Nubus can use the UDM HTTP REST API in the Directory Manager to write data to the directory service.

Fig. 5.8 Data flow for creating UDM objects between component functions