3. Components

This section describes the functional components of Univention Nubus for Kubernetes. You find information about what each functional component does in detail, what services it offers to other components, what internals exist that are interesting to know, and how everything relates together.

Like the other sections, the description of the functional components uses the ArchiMate enterprise architecture modeling notation.

Information about used notation

This section uses concepts from the ArchiMate enterprise architecture modeling notation across the application and technology layers.

From the business layer it uses the following concepts:

• Business Role

From the application layer it uses the following concepts:

• Application Component

• Application Interface

• Application Service

• Application Process

• Application Function

• Application Event

• Data Object

From the technology layer it uses the following concepts:

• System Software

• Artifact

From the relationships it uses the following concepts:

• Composition

• Aggregation

• Realization

• Assignment

• Flow

• Serving

• Trigger

• Access

For more information on these ArchiMate concepts, refer to the following sections in Univention Corporate Server Architecture [2]:

• Business layer

• Application layer

• Technology layer

• Relationships

• 3.1. Authorization Service
  • 3.1.1. Policy-based authorization
  • 3.1.2. Management of authorization rules
  • 3.1.3. Registration of Authorization Service in Identity Provider
  • 3.1.4. Storage
  • 3.1.5. Dependencies
• 3.2. Directory Manager
  • 3.2.1. Internal functions
  • 3.2.2. Authentication and authorization for CRUD operations
  • 3.2.3. Populate data on initial startup of Nubus
• 3.3. End User Self Service
  • 3.3.1. Self Service Consumer
  • 3.3.2. User account profile
  • 3.3.3. User self registration
  • 3.3.4. User password reset
• 3.4. Identity Provider
  • 3.4.1. Single sign-on / single sign-out
  • 3.4.2. Identity Store
  • 3.4.3. Keycloak Extensions
    • 3.4.3.1. Brute force protection
    • 3.4.3.2. New device notification
• 3.5. Identity Store and Directory Service
  • 3.5.1. Information types in identity store
  • 3.5.2. Provide user account and user group information
  • 3.5.3. Notify about changes to directory objects
  • 3.5.4. Write data to the identity store
  • 3.5.5. Store configuration data
• 3.6. Intercom Service
• 3.7. Management UI
  • 3.7.1. UMC Gateway
  • 3.7.2. UMC Server
• 3.8. Portal Service
  • 3.8.1. Portal Server
  • 3.8.2. Portal Frontend
  • 3.8.3. Portal Consumer
  • 3.8.4. Portal Announcement
  • 3.8.5. Notifications API
  • 3.8.6. Central Navigation API
• 3.9. Provisioning Service
  • 3.9.1. UDM Listener
  • 3.9.2. UDM Transformer
  • 3.9.3. Dispatcher
  • 3.9.4. Consumer Messages HTTP REST API
  • 3.9.5. Consumer Registration HTTP REST API
  • 3.9.6. Prefill Service
  • 3.9.7. Nubus initial startup
• 3.10. Connectors
  • 3.10.1. IAM Connector
  • 3.10.2. Nubus Directory Importer
    • 3.10.2.1. Import
    • 3.10.2.2. Data flow
    • 3.10.2.3. Trust relationship for authentication
• 3.11. Dependencies
  • 3.11.1. Functional component level
    • 3.11.1.1. Internal view functional component
    • 3.11.1.2. External view functional component
  • 3.11.2. Application component level
    • 3.11.2.1. Internal view application component level
    • 3.11.2.2. External view application component level