Skip to content

Type 1b) Manual Initial Configuration with CRID and OTP

The following step-by-step instructions will guide you through the manual initial configuration if you don't have a sedex participant certificate but received temporary credentials CRID and OTP.

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: 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_CRID=YOUR-CERTIFICATE-REQUEST-ID
SEDEX_OTP=YOUR-ONE-TIME-PASSWORD

SEDEX_ID=1-1234-1
SEDEX_CRID=2d-9b-31-18-68
SEDEX_OTP=BSAH-YAKO-JGHL-KIDE

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.