Nubus for Kubernetes - Architecture Manual 1.0.1

Dependencies

3.11. Dependencies#

This section describes the internal dependencies of Nubus for Kubernetes, and the external dependencies regarding third-party applications, from the perspective of Nubus. Linked sections provide detailed information about component features and interfaces. This section distinguishes between internal and external components, including detailed information about the dependencies.

Tip

The figures in this section mostly use the ArchiMate Serving relationship, which represents a component that provides its functionality to another component. The models show the dependencies between the components.

3.11.1. Functional component level#

This section gives an overview about the dependencies on the level of the Nubus functional components with an internal view and an external view.

3.11.1.1. Internal view functional component#

This section gives an overview about the dependencies on the Nubus functional components, as shown in Fig. 3.50. For a view including the application components inside the functional components, see Internal view application component level.

Internal view of the component dependencies on the functional component level

Fig. 3.50 Internal view of the component dependencies on the functional component level#

Authorization service

Depends on the functionality of:

End User Self Service

The End User Self Service depends on the functionality of:

Management UI

It depends on the functionality of:

It provides its functionality to:

Directory Manager

It depends on the functionality of:

It provides its functionality to:

IAM Connector

The IAM Connector depends on the functionality of the following components:

Portal Service

The Portal Service depends on the functionality of following components:

It provides functionality to the End User Self Service.

Identity Store and Directory Service

The Identity Store and Directory Service is the central component. It provides its functionality to following components:

Identity Provider

It depends on the functionality of:

It provides its functionality to:

Provisioning Service

The Provisioning Service depends on the functionality of the following components:

It provides its functionality to:

Intercom Service

The Intercom Service depends on the functionality of the Identity Provider.

3.11.1.2. External view functional component#

This section describes the dependencies between the involved internal Nubus components and external components, such as Third-party applications not part of Nubus, as shown in Fig. 3.51. The term Third-party application is a placeholder for any application external to Nubus.

External components dependencies

Fig. 3.51 External components dependencies#

The following functional components of Nubus for Kubernetes provide their functionality to third-party applications:

The following functional components of Nubus for Kubernetes can use functionality of third-party applications:

3.11.2. Application component level#

This section gives an overview about the dependencies on the application component level of the Nubus functional components. It offers a separate internal and external view. Application components are active components that are part of the functional components.

3.11.2.1. Internal view application component level#

This section describes the internal dependencies on the behavior level of the functional components. It shows the behaviors of components that depends on behavior functionality of another component. It covers the following components.

Authorization Service

It provides two HTTP REST APIs and the Guardian Management UI

The Guardian Authorization HTTP REST API, uses functionality from the UDM HTTP REST API in the Directory Manager to consume identity data. Second, it uses the functionality of Keycloak in the Identity Provider.

The Guardian Management HTTP REST API also uses functionality from Keycloak.

The Guardian Management UI uses functionality from the UMC-Server in the Management UI.

Directory Manager

It provides the UDM Library and the UDM HTTP REST API.

The UDM Library uses functionality from the LDAP Server in the Identity Store and Directory Service.

The UDM HTTP REST API uses the following components:

  • LDAP Server

  • UDM Library

The following components use functionality from the UDM HTTP REST API:

The following components use functionality from the UDM Library:

Identity Store and Directory Service

The LDAP Server is a key component in Nubus. It provides its functionality to various components, as you can see from the centered position in Fig. 3.52.

Identity Provider

The component Keycloak has the following dependencies: It uses the functionality of the LDAP Server in the Identity Store and Directory Service.

The following components use functionality of Keycloak:

  1. Nubus Directory Importer

  2. Guardian Management HTTP REST API in Authorization Service

Provisioning Service

It uses functionality from the following components:

  1. Prefill Service uses functionality from the UDM HTTP REST API in the Directory Manager.

  2. UDM Transformer uses functionality from the UDM Library.

  3. UDM Listener uses functionality from the LDAP Server in the Identity Store and Directory Service.

The following components use functionality from the Events and Consumer API:

Portal Service

It uses functionality from the following components:

Management UI

The UMC Server uses functionality from the following components:

The UMC Server provides its functionality to the following components:

End User Self Service

It depends on the following components:

Internal components dependencies details

Fig. 3.52 Internal components dependencies details#

3.11.2.2. External view application component level#

The section describes the dependencies on the behavior level between internal components and third-party applications, as shown in Fig. 3.53. It covers the following components:

Authorization Service

The Third-party application, not part of Nubus can use the Guardian Authorization HTTP REST API.

Directory Manager

The Third-party application, not part of Nubus can use the UDM HTTP REST API.

Identity Store and Directory Service

The Third-party application, not part of Nubus can use the LDAP Server.

Provisioning Service

The Third-party application, not part of Nubus can use the functionality of the Consumer Messages HTTP REST API.

Identity Provider

The Third-party application, not part of Nubus can use the functionality of Keycloak.

Intercom Service

The Third-party application, not part of Nubus can use the Intercom Service.

Nubus Directory Importer

The Third-party application, not part of Nubus can provide functionality to the Nubus Directory Importer, if the functionality is of use for it.

External components dependencies

Fig. 3.53 External components dependencies details#

On this page