Versions Compared

Old Version 84

changes.mady.by.user slavek.licehammer.2@at.internet2.edu

Saved on

compared with

New Version Current

changes.mady.by.user slavek.licehammer.2@at.internet2.edu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ContainerContentDescription
sourcesMariaDB server

This serves as an example of source systems. MariaDB here hosts SIS_PERSONS, SIS_AFFILIATIONS and SIS_COURSES tables that contain data about approximately 100 persons, their departmental membership, affiliations and course enrollment. The data are the same as present in TIER Grouper sample, only the form is different (here SQL, in Grouper sample LDAP+SQL).

midpoint_servermidPoint softwareThis is the standard container providing midPoint functionality.
midpoint_dataPostreSQL serverThis container provides the repository for midPoint. It is separate, so it can be replaced as needed: either with a container hosting any other supported database, or with a non-dockerized repository (on-premises or in cloud).
grouper_uiGrouper softwareHere the Grouper UI executes.
grouper_wsGrouper softwareHere the Grouper WS (Web Services) executes.
grouper_daemonGrouper softwareHere the Grouper loader jobs execute.
grouper_dataMariaDB serverThis is the repository for Grouper. In a similar way as for midPoint, it is separate so that it can be replaced as needed.
grouper_data_initinitInitialize data in grouper. Create loader groups and setup midPoint provisioner. This container can be replaced by static configuration, if needed.
directory389ds serverThis is the central LDAP directory. It is used by Grouper as a primary source of subjects and "imported" group membership (from source systems and optionally from midPoint). It is also used by Shibboleth IdP as source of authentication information.
mqRabbitMQThis provides near real-time synchronization between Grouper and midPoint and optionally target systemsRabbitMQ server. It's part of the Grouper deployment and not relevant for this demo.
idpShibboleth IdPHere Shibboleth IdP executes, providing authentication service for Grouper and (in the future) also for midPoint.
idp_vol_initinitPreparing configuration files like metadata for Shibboleth IdP. This container can be replaced by static configuration, if needed.
proxyNGINXHTTP proxy for accessing midPoint, Grouper and Shibboleth IdP.
beaconTAP BeaconInCommon TAP Beacon.
data_initinitThis container is responsible for initialization of midpoint_data container.
prereqinitConfiguration files initialization for other containers. It generates certificates, keystores and database password. This container can be replaced by static configuration, if needed.

...