$ cd demo/simple
$ docker-compose up --build
Simple demo
This demo shows Midpoint with PostgreSQL repository. Midpoint contains csv-resource as the source and openldap-resource as the target.
The image can be found in the Evolveum/midpoint-docker GitHub project.
Starting
After docker-compose up
command successfully finishes you should see something like this on the console:
simple_midpoint_server_1 | 2019-02-22 15:07:50,222 [] [main] INFO (org.springframework.boot.web.embedded.tomcat.TomcatWebServer): Tomcat started on port(s): 8080 (http) with context path '/midpoint'
simple_midpoint_server_1 | 2019-02-22 15:07:50,230 [] [main] INFO (com.evolveum.midpoint.web.boot.MidPointSpringApplication): Started MidPointSpringApplication in 74.425 seconds (JVM running for 77.109)
Now you can log into midPoint using http://localhost:8080/midpoint URL, with an user of administrator
and a password of 5ecr3t
.
Also you can log into OpenLDAP server using a host of localhost and _a port of 389_, with a Bind DN of cn=admin,dc=evolveum,dc=com and a Bind password of secret.
During starting, in Midpoint is configured two resources, one object template, one role and are started two script for testing connection on reseouces and one for import accounts from csv-resources. If user is imported from csv file, then he automaticly get role, which insure create user account in OpenLdap server.
You can safely ignore console messages like this:
simple_midpoint_server_1 | ERROR: could not serialize access due to read/write dependencies among transactions
simple_midpoint_server_1 | DETAIL: Reason code: Canceled on identification as a pivot, during write.
simple_midpoint_server_1 | HINT: The transaction might succeed if retried.
This is a part of standard midPoint conflict resolution process. The mentioned transactions are really retried and they succeed eventually.
Containers
The demo/simple
composition contains the following containers:
Container name | Description |
---|---|
|
This is the standard container providing midPoint functionality. It contains standalone Tomcat running midPoint application. |
|
This container hosts midPoint repository; this time it is implemented on PostgreSQL 9.5 database. |
|
OpenLDAP server used as the target. |
Communication
The containers publish the following TCP ports. (Port mapped to localhost denotes the mapping of container port to the host port where it can be reached from the outside.)
Container | Port number | Port mapped to localhost | Description |
---|---|---|---|
|
8080 |
8080 |
HTTP port to be used to connect to midPoint application |
|
5432 |
5432 |
Port used to connect to the PostgreSQL database |
|
389 |
389 |
Port used to connect to the OpenLDAP server |
Docker volumes
The following volumes are created to persist data and other relevant files.
Volume name | Description | Used by container |
---|---|---|
|
The midPoint home directory. Contains schema extensions, logs, custom libraries, custom ConnId connectors, and so on. |
|
|
Volume hosting PostgreSQL database used by midPoint. |
|
|
Volume hosting LDAP database. |
|
|
Volume hosting the corresponding LDAP config files. |
|
Configuring the composition
The following configuration properties are supported. Please refer to the main documentation page for their explanation.
Property | Default value |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You can tailor these to your needs.
The following Docker secrets are used:
Secret | Location |
---|---|
|
|
|
|
The following configuration files are used:
Target file | Source location | Description |
---|---|---|
|
midpoint_server/container_files/mp-home/ |
When |
You can modify or replace these files as needed.