Type 1a) Manual Initial Configuration with Existing Certificate¶
The following step-by-step instructions will guide you through the manual initial configuration if you already have a sedex participant certificate and the corresponding keystore (P12 file).
Warning: Execute Initial Configuration only once
The initial configuration must be executed exactly once, before the very first start of the sedex Client container.
If an initial configuration is performed again later, misconfigurations can result and in the worst case important data such as keystores or sedex messages could be lost.
Step 1: Create directories for the permanent storage¶
Create the two permanent storage directories "sedex-interface" and "sedex-data" in the file system of the host where the sedex Client container will run. These directories will later on be attached to the sedex Client container with a Docker bind mount, allowing the container to persist its data in these directories.
mkdir /path/to/sedex-interface
mkdir /path/to/sedex-data
mkdir /home/data/sedex-interface-1-1234-1
mkdir /home/data/sedex-data-1-1234-1
Step 2: Provide the existing keystore file (P12)¶
Copy the sedex keystore file (PKCS12/P12 format containing the private key and certificate) into the root of the "sedex-data" directory.
$ cp /path/to/credentials/YOUR-KEYSTORE-FILE.p12 /path/to/sedex-data/
$ cp /home/data/credentials/1-1234-1.p12 /home/data/sedex-data-1-1234-1/
Step 3: Create the "init.conf" file which contains the initial configuration parameters¶
With a text editor (e.g. "nano") create a plain text file named "init.conf" in the "sedex-data" directory:
$ nano /path/to/sedex-data/init.conf
$ nano /home/data/sedex-data-1-1234-1/init.conf
Add the following three configuration parameters (with values appropriate to your situation) to your "init.conf" file and save it:
SEDEX_ID=YOUR-SEDEX-ID
SEDEX_KEYSTORE_FILENAME=YOUR-KEYSTORE-FILE.p12
SEDEX_KEYSTORE_PASSWORD=YOUR-PASSWORD
SEDEX_ID=1-1234-1
SEDEX_KEYSTORE_FILENAME=1-1234-1.p12
SEDEX_KEYSTORE_PASSWORD=ALFJZIPNXG
init.conf will be deleted automatically at the end of the initial configuration
After the first successful start of the sedex Client, the "init.conf" file will be automatically deleted after its content has been imported into the operational sedex configuration files.
Configuring an outgoing HTTP proxy
If an HTTP proxy is required to access the Internet, a proxy server can optionally be defined in the init.conf file (see section Optional Parameters)
or be manually added later on as part of the configuration of the sedex Client (see section Configuration Options - How to Configure).
Now everything is ready to initialize the sedex Client Docker container. The container will do this automatically on its first normal startup. So you can continue with Phase 2 - Run.