Commit 10b5056e authored by Benny Prange's avatar Benny Prange
Browse files

Release eumw-1.0.6

parent 8aab799f
......@@ -14,3 +14,4 @@ cd6877486ad7373dae2fec12f9f74d19e78d1110 eumw-1.0.4
0000000000000000000000000000000000000000 eumw-1.0.4
76f405023426c019aee600be45f72020a1f66159 eumw-1.0.4
6220fdf6481bec6cbc12535f3e3ac49ac6bbecff eumw-1.0.5-rc.1
e98bc5c6b60496c8d6533c5655626ba39701cf37 eumw-1.0.5
version: '3'
services:
configuration-wizard:
image: "governikus/eidas-configuration-wizard:1.0.5"
image: "governikus/eidas-configuration-wizard:1.0.6"
ports:
- "443:8080"
environment:
......
version: '3'
services:
configuration-wizard:
image: "governikus/eidas-configuration-wizard:1.0.5"
image: "governikus/eidas-configuration-wizard:1.0.6"
ports:
- "8080:8080"
volumes:
......
FROM governikus/eidas-base-container:1.0.5
FROM governikus/eidas-base-container:1.0.6
MAINTAINER Benny Prange <benny.prange@governikus.de>
# NOTE: Some ENV variables are set in the parent "eidas-base-image"
......
......@@ -14,7 +14,7 @@
<parent>
<groupId>de.governikus.eumw</groupId>
<artifactId>eumw</artifactId>
<version>1.0.5</version>
<version>1.0.6</version>
</parent>
<artifactId>configuration-wizard</artifactId>
......
......@@ -14,7 +14,7 @@
<parent>
<artifactId>eumw</artifactId>
<groupId>de.governikus.eumw</groupId>
<version>1.0.5</version>
<version>1.0.6</version>
</parent>
<artifactId>database-migration</artifactId>
......
......@@ -33,4 +33,9 @@ Changelog
- eIDAS Middleware: The URL for the entityID in the metadata must now be set in the configuration. Add SERVER_URL=https://host:port to eidasmiddleware.properties.
- Configuration Wizard: Adapt for new configuration value. Use the value from the eID configuration page.
- Configuration Wizard: Ensure that only one connector metadata file is saved.
- Configuration Wizard: Ensure that the original filenames are used when loading and saving a previous configuration.
\ No newline at end of file
- Configuration Wizard: Ensure that the original filenames are used when loading and saving a previous configuration.
* 1.0.6
- eIDAS Middleware: Fix bug introduced with version 1.0.5 where two URLs in the SAML response were switched.
- eIDAS Middleware: Improve logging in case of unparsable authentication request.
......@@ -56,7 +56,7 @@ In case you are using your own environment, copy the JAR file to a folder of you
You can start the application with the following command::
java -jar configuration-wizard-1.0.5.jar
java -jar configuration-wizard-1.0.6.jar
This way the configuration wizard will be available at `http://localhost:8080/config-wizard.`
......@@ -81,7 +81,7 @@ to run the wizard again whenever you need it.
To run the configuration wizard, execute the following command.
It will mount the named volume in the container so that the configuration wizard can store the configuration in the volume. ::
docker run --rm -it -v eidas-configuration:/opt/eidas-middleware/configuration -p 8080:8080 --name eidas-configuration-wizard governikus/eidas-configuration-wizard:1.0.5
docker run --rm -it -v eidas-configuration:/opt/eidas-middleware/configuration -p 8080:8080 --name eidas-configuration-wizard governikus/eidas-configuration-wizard:1.0.6
Running this command the configuration wizard will be available on http://localhost:8080/config-wizard.
......@@ -95,7 +95,7 @@ with the alias ``localhost`` and the password ``123456`` for the keystore and th
You can also use PKCS12 keystores,
in this case you must change the value of ``SERVER_SSL_KEY_STORE_TYPE`` to ``PKCS12``. ::
docker run --rm -it -v eidas-configuration:/opt/eidas-middleware/configuration -v /home/user/keystore.jks:/opt/eidas-middleware/keystore.jks -p 443:8080 -e SERVER_SSL_KEY_STORE=file:/opt/eidas-middleware/keystore.jks -e SERVER_SSL_KEY_STORE_TYPE=JKS -e SERVER_SSL_KEY_STORE_PASSWORD=123456 -e SERVER_SSL_KEY_ALIAS=localhost -e SERVER_SSL_KEY_PASSWORD=123456 --name eidas-configuration-wizard governikus/eidas-configuration-wizard:1.0.5
docker run --rm -it -v eidas-configuration:/opt/eidas-middleware/configuration -v /home/user/keystore.jks:/opt/eidas-middleware/keystore.jks -p 443:8080 -e SERVER_SSL_KEY_STORE=file:/opt/eidas-middleware/keystore.jks -e SERVER_SSL_KEY_STORE_TYPE=JKS -e SERVER_SSL_KEY_STORE_PASSWORD=123456 -e SERVER_SSL_KEY_ALIAS=localhost -e SERVER_SSL_KEY_PASSWORD=123456 --name eidas-configuration-wizard governikus/eidas-configuration-wizard:1.0.6
Because the application is now bound to the host in port 443,
the configuration wizard is available at https://localhost/config-wizard.
......
......@@ -50,8 +50,8 @@ Using the eIDAS Demo Application
To use the eIDAS Demo Application, start by running the eIDAS Demo Application.
#. Change to the correct directory where the aforementioned configuration is present.
#. If not present, copy the ``eidas-demo-1.0.5.jar`` file in this directory.
#. Start the application by executing ``java -jar eidas-demo-1.0.5.jar``.
#. If not present, copy the ``eidas-demo-1.0.6.jar`` file in this directory.
#. Start the application by executing ``java -jar eidas-demo-1.0.6.jar``.
Now you must configure your eIDAS Middleware to communicate with the eIDAS Demo Application.
......@@ -88,7 +88,7 @@ Also bear in mind that you must use the path of the container file system in the
To run the middleware, execute the following command after you have prepared the configuration, certificate and keystores::
docker run --rm -it -v /path/to/your/config-directory:/opt/eidas-middleware/config -p 8080:8080 governikus/eidas-demo-application:1.0.5
docker run --rm -it -v /path/to/your/config-directory:/opt/eidas-middleware/config -p 8080:8080 governikus/eidas-demo-application:1.0.6
Now you can follow the steps above to configure and test the eIDAS Middleware.
......
......@@ -84,13 +84,13 @@ To run the eIDAS Middleware, execute the following command.
It will mount the named volumes containing the database and configuration in the container
and the application will be available on port 8443. ::
docker run --rm -it -v eidas-configuration:/opt/eidas-middleware/configuration -v eidas-database:/opt/eidas-middleware/database -p 8443:8443 --name eidas-middleware-application governikus/eidas-middleware-application:1.0.5
docker run --rm -it -v eidas-configuration:/opt/eidas-middleware/configuration -v eidas-database:/opt/eidas-middleware/database -p 8443:8443 --name eidas-middleware-application governikus/eidas-middleware-application:1.0.6
To stop and remove the container, just hit ``CTRL+C``.
To keep the container running longer without being attached to the STDOUT and STDERR, change the command to the following::
docker run -d -v eidas-configuration:/opt/eidas-middleware/configuration -v eidas-database:/opt/eidas-middleware/database -p 8443:8443 --name eidas-middleware-application governikus/eidas-middleware-application:1.0.5
docker run -d -v eidas-configuration:/opt/eidas-middleware/configuration -v eidas-database:/opt/eidas-middleware/database -p 8443:8443 --name eidas-middleware-application governikus/eidas-middleware-application:1.0.6
For more information on starting and stopping containers and viewing the logs,
see the `Docker Docs <https://docs.docker.com/engine/reference/run/>`_.
......@@ -134,7 +134,7 @@ Scalability
^^^^^^^^^^^
The performance of the eIDAS Middleware improves by adding more memory (RAM) and using a faster CPU.
In case the memory configuration has changed, the server needs to be restarted.
To start the JVM with more memory, add ``-Xmx`` with the new maximum memory size to the start command, e.g. ``java -Xmx8g -jar eidas-middleware-1.0.5.jar`` for 8 GB.
To start the JVM with more memory, add ``-Xmx`` with the new maximum memory size to the start command, e.g. ``java -Xmx8g -jar eidas-middleware-1.0.6.jar`` for 8 GB.
Monitoring
......@@ -188,5 +188,5 @@ The configuration file must contain the following values. The first three values
Before running the migration tool, please create a backup of your database.
Stop the eIDAS Middleware Application and copy the database file to your backup location, e.g. ``cp /opt/eidas-middleware/database/eidasmw.mv.db /path/to/your/backup-location/eidasmw.mv.db``.
To perform the migration, copy the database migration JAR file to the directory where your configuration file is available and execute the command ``java -jar database-migration-1.0.5.jar``.
To perform the migration, copy the database migration JAR file to the directory where your configuration file is available and execute the command ``java -jar database-migration-1.0.6.jar``.
If there are errors in the log output, please send the complete log output and some information on your environment to eidas-middleware@governikus.com.
......@@ -59,9 +59,9 @@ author = u'Hartje Bruns'
# built documents.
#
# The short X.Y version.
version = '1.0.5'
version = '1.0.6'
# The full version, including alpha/beta/rc tags.
release = '1.0.5'
release = '1.0.6'
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
......
......@@ -3,7 +3,7 @@ FROM governikus/zulu-openjdk:8u172
MAINTAINER Benny Prange <benny.prange@governikus.de>
# Define the application version for the subsequent application images
ENV VERSION=1.0.5
ENV VERSION=1.0.6
# Define the spring boot configuration directory
ENV CONFIG_DIR=/opt/eidas-middleware/configuration
......
......@@ -14,7 +14,7 @@
<parent>
<groupId>de.governikus.eumw</groupId>
<artifactId>eumw</artifactId>
<version>1.0.5</version>
<version>1.0.6</version>
</parent>
<artifactId>eid-service</artifactId>
......
......@@ -14,7 +14,7 @@
<parent>
<groupId>de.governikus.eumw</groupId>
<artifactId>eumw</artifactId>
<version>1.0.5</version>
<version>1.0.6</version>
</parent>
<artifactId>eidas-common</artifactId>
......
......@@ -29,7 +29,7 @@ UNSIGNED_ASSERTIONCONSUMER_URL=The request specifies AssertionConsumerURL but is
ASSERTIONCONSUMER_URL_CHANGE_NOT_ALLOWED=The request specifies AssertionConsumerURL but this is not allowed by the configuration.
SIGNATURE_CHECK_FAILED=The signature check failed.
SIGNATURE_MISSING=The SAML request or response was not signed.
ILLEGAL_REQUEST_SYNTAX=It was not possible to parse the SAML request.
ILLEGAL_REQUEST_SYNTAX=It was not possible to parse the SAML request: {0}.
ECARD_ERROR=An error was reported from eCardAPI: {0}
DUPLICATE_REQUEST_ID=The request ID {0} has been used before.
EID_ERROR=An error was reported from eID-Server: {0}
......@@ -45,4 +45,4 @@ PROXY_COUNT_EXCEEDED=The proxy count raced 0
NO_SUPPORTED_IDP=Non of the IdPs given in the IDPList in the SAML Request are supported.
EID_MISSING_TERMINAL_RIGHTS=The client requested to read the attributes {0} from the nPA, which is not allowed by the CVC.
EID_MISSING_ARGUMENT=The requests misses the argument for {0}.
REQUEST_DENIED=The request was denied.
\ No newline at end of file
REQUEST_DENIED=The request was denied.
version: '3'
services:
eidas-demo-application:
image: "governikus/eidas-demo-application:1.0.5"
image: "governikus/eidas-demo-application:1.0.6"
ports:
- "8080:8080"
volumes:
......
FROM governikus/eidas-base-container:1.0.5
FROM governikus/eidas-base-container:1.0.6
MAINTAINER Benny Prange <benny.prange@governikus.de>
# NOTE: Some ENV variables are set in the parent "eidas-base-image"
......
......@@ -14,7 +14,7 @@
<parent>
<groupId>de.governikus.eumw</groupId>
<artifactId>eumw</artifactId>
<version>1.0.5</version>
<version>1.0.6</version>
</parent>
<artifactId>eidas-demo</artifactId>
......
version: '3'
services:
middleware-application:
image: "governikus/eidas-middleware-application:1.0.5"
image: "governikus/eidas-middleware-application:1.0.6"
ports:
- "8443:8443"
volumes:
......
FROM governikus/eidas-base-container:1.0.5
FROM governikus/eidas-base-container:1.0.6
MAINTAINER Benny Prange <benny.prange@governikus.de>
# Define the location of the configuration directory inside of the container
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment