The fiskaltrust Launcher is an application that hosts the packages of the fiskaltrust Middleware, a modular fiscalization and POS platform that can be embedded into POS systems to suffice international fiscalization regulations.
Warning This all-new fiskaltrust Launcher is currently in development. We plan to release a preview version to interested customers soon - please reach out to us in the discussion section if you want to participate.
You can track the ongoing development of the first release in the project's backlog and board.
Middleware packages each provide specific fiscalization-, data source- and security device implementations. These package can be aggregated into a configuration container (Cashbox) in the fiskaltrust Portal. The Launcher then uses this configuration to decide which packages to download and run, and provides configurable hosted endpoints so that the POS software can communicate with them (e.g. gRPC or HTTP).
Below, we illustrate a minimal sample configuration with the international SQLite Queue package (with a configured HTTP endpoint) and a German Signature Creation Unit (with a gRPC endpoint) that abstracts a Swissbit TSS.
Download the latest release from GitHub. We always recommend using the latest release to benefit from the newest improvements. Unzip the downloaded release.
You can also download the Launcher from the fiskaltrust Portal (only sandbox at the moment), the Launcher will come with a preconfigured launcher.configuration.json file.
The download will contain the fiskaltrust.Launcher executable and launcher-test, launcher-install, launcher-uninstall .cmd or .sh scripts and a launcher-migrate.cmd script on Windows.
- The
launcher-test.cmdorlauncher-test.shscript can be used to test the Launcher. It will start the Launcher with--log-levelparameter set to debug. - The
launcher-install.cmdorlauncher-install.shscript can be used to install the Launcher as a service. - The
launcher-uninstall.cmdorlauncher-uninstall.shscript can be used to uninstall the Launcher as a service. - The
launcher-migrate.cmdscript can be used to from migrate the Launcher 1.3 to the Launcher 2.0 (See Migration Script for more information).
Alternatively you can start the Launcher via the command line:
# Will use the configuration file `launcher.configuration.json` in the current directory
fiskaltrust.Launcher.exe run
# Will use the cashbox id and access token from the cli parameters
fiskaltrust.Launcher.exe run --cashbox-id <cashboxid> --access-token <accesstoken> --sandboxTo stop the Launcher press Ctrl + C.
See help for other start parameters:
fiskaltrust.Launcher.exe run --helpSee help for other available commands:
fiskaltrust.Launcher.exe --help
See CLI for more information.
On Debian based Linux systems the Launcher can also be installed via apt-get . The executable will be installed at /usr/bin/fiskaltrust.Launcher and can be run like that fiskaltrust.Launcher --help .
curl -L http://downloads.fiskaltrust.cloud/apt-repo/KEY.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/fiskaltrust-archive-keyring.gpg > /dev/null
echo "deb [signed-by=/usr/share/keyrings/fiskaltrust-archive-keyring.gpg] https://downloads.fiskaltrust.cloud/apt-repo stable main" | sudo tee /etc/apt/sources.list.d/fiskaltrust.list
sudo apt update
sudo apt install fiskaltrust-middleware-launcherWhen installed this way the self-update functionality of the launcher is disabled and it has to be updated via
apt-get.sudo apt update && sudo apt install --only-upgrade fiskaltrust-middleware-launcher
Before switching from a 1.3 Launcher to a Launcher 2.0, please update the Queues, SCUs and Helpers to the latest packages.
Then download the new launcher from the Portal or the GitHub release page.
Run the uninstall-service.cmd or uninstall-service.sh command to deinstall the old launcher.
If you did not download the Launcher from the Portal manually create the configuration file, and make sure to include the cashboxId and accessToken and to set sandbox to true if needed.
In the new launcher folder execute the launcher-install.cmd or launcher-install.sh script or run the following command .\fiskaltrust.Launcher.exe install.
To check that the switch was successful, e.g. try sending receipt to the middleware using our Postman collection.
On Windows we provide a launcher-migrate.cmd script that can be used to migrate the Launcher 1.3 to the Launcher 2.0.
This script will migrate an existing service installation of the Launcher 1.3 to the Launcher 2.0.
To run this script unzip the downloaded Launcher 2.0 files into the folder containing the old Launcher 1.3.
The folder should now contain at least the following files:
. ├─ fiskaltrust.Launcher.exe ├─ launcher.configuration.json ├─ launcher-migrate.cmd └─ fiskaltrust.exe
And then run the launcher-migrate.cmd script as an administrator.
The script will do the following:
- Find the service of the old Launcher (
fiskaltrust.exe) - Stop and uninstall the service
- Install the new Launcher 2.0 as a service using the same service name as the old Launcher
- Backup the old Launcher 1.3 files to the
.backupfolder
The Launcher 2.0 configuration is now read from a JSON file ( launcher.configuration.json in the working directory per default). The configuration has to be created manually.
This file can be set via the --launcher-configuration-file cli argument.
The configuration file should contain the following config keys:
{
"ftCashBoxId": "<ftCashBoxId>", // string
"accessToken": "<accessToken>", // string
"launcherPort": "<launcherPort>", // int (default: 0)
"serviceFolder": "<serviceFolder>", // string (default-windows: "C:/ProgramData/fiskaltrust", default-linux: "/var/lib/fiskaltrust", default-macos: "/Library/Application Support/fiskaltrust")
"sandbox": "<sandbox>", // bool (default: true)
"useOffline": "<useOffline>", // bool (default: false)
"launcherVersion": "<launcherVersion>", // string (default: null)
"logFolder": "<logFolder>", // string (default: "<serviceFolder>/logs")
"logLevel": "<logLevel>", // string (default: "Information")
"packageCache": "<packageCache>", // string (default: "<serviceFolder>/cache")
"packagesUrl": "<packagesUrl>", // string (default: "https://packages-2-0[-sandbox].fiskaltrust.cloud")
"helipadUrl": "<helipadUrl>", // string (default: "https://helipad[-sandbox].fiskaltrust.cloud")
"downloadRetry": "<downloadRetry>", // int (default: 1)
"sslValidation": "<sslValidation>", // bool (default: false)
"proxy": "<proxy>", // string (default: null)
"configurationUrl": "<configurationUrl>", // string (default: "https://configuration[-sandbox].fiskaltrust.cloud")
"downloadTimeoutSec": "<downloadTimeoutSec>", // int (default: 15)
"processHostPingPeriodSec": "<processHostPingPeriodSec>", // int (default: 10)
"cashboxConfigurationFile": "<cashboxConfigurationFile>", // string (default: "<serviceFolder>/service/Configuration-<ftCashBoxId>.json")
"useHttpSysBinding": "useHttpSysBinding", // bool (default: false)
}All of these config keys can be overridden using the corresponding cli arguments.
The run command of the fiskaltrust.Launcher is used to execute the launcher, providing users with various options to configure its behaviour and logging details.
| Option | Description | Default |
|---|---|---|
--cashbox-id <cashbox-id> |
Specifies the ID of the cashbox. | |
--access-token <access-token> |
Token used for authentication. | |
--sandbox |
Enables sandbox mode. | false |
--log-folder <log-folder> |
Path to the folder where logs will be saved. | "<service-folder>/logs" |
--log-level <level> |
Determines the logging level. Accepts values like Critical, Debug, etc. | "Information" |
--launcher-configuration-file <file> |
Path to the launcher configuration file. | "launcher.configuration.json" |
--legacy-configuration-file <file> |
Path to the legacy configuration file. | "fiskaltrust.exe.config" |
--merge-legacy-config-if-exists |
If set, merges legacy configuration if it exists. | true |
--launcher-port <port> |
Specifies the port which the launcher will use for internal communication. A dynamic binding is used by default. | 0 |
--use-offline |
Enables offline mode. | false |
--service-folder <service-folder> |
Path to the service folder. | Windows: "C:/ProgramData/fiskaltrust"Linux: "/var/lib/fiskaltrust"MacOS: "/Library/Application Support/fiskaltrust" |
--configuration-url <configuration-url> |
URL to fetch the configuration from. | "https://configuration[-sandbox].fiskaltrust.cloud" |
--packages-url <packages-url> |
URL to fetch packages from. | "https://packages-2-0[-sandbox].fiskaltrust.cloud" |
--package-cache <package-cache> |
Cache directory for the packages. | "<serviceFolder>/cache" |
--helipad-url <helipad-url> |
URL for the helipad. | "https://helipad[-sandbox].fiskaltrust.cloud" |
--download-timeout-sec <download-timeout-sec> |
Timeout for downloads in seconds. | 15 |
--download-retry <download-retry> |
Number of times to retry a failed download. | 1 |
--ssl-validation |
Validates SSL certificates. | true |
--proxy <proxy> |
Proxy server details. | |
--processhost-ping-period-sec <processhost-ping-period-sec> |
Ping period for the process host in seconds. | 10 |
--cashbox-configuration-file <cashbox-configuration-file> |
Path to the cashbox configuration file. | ""<serviceFolder>/service/Configuration-<ftCashBoxId>.json" |
--tls-certificate-path <tls-certificate-path> |
Path to the TLS certificate. | |
--tls-certificate-base64 <tls-certificate-base64> |
Base64 encoded TLS certificate. | |
--tls-certificate-password <tls-certificate-password> |
Password for the TLS certificate. | |
--use-http-sys-binding <use-http-sys-binding> |
Uses HTTP sys binding. | false |
--use-legacy-data-protection <use-legacy-data-protection> |
Enables use of legacy data protection. | false |
-? , -h , --help |
Displays help and usage information. |
The config get command of the fiskaltrust.Launcher can be used to get the current values of the Launcher configuration file.
Usage:
fiskaltrust.Launcher.exe config get
fiskaltrust.Launcher.exe config --launcher-configuration-file <launcher-configuration-file> getTo use an other location of the configuration file.
The config set command of the fiskaltrust.Launcher can be used to set configuration values in the Launcher configuration file.
Usage:
fiskaltrust.Launcher.exe config set --<config-key> <value>E.g.
fiskaltrust.Launcher.exe config set --log-leve Debug
The doctor command of the fiskaltrust.Launcher can be used to for troubleshooting launcher problems. It can be run with the same cli parameters as the run command.
The doctor command should give the following output when run successfully:
[10:11:09 INF] ✅ Parse launcher configuration
[10:11:10 INF] ✅ Load ECDH Curve
[10:11:10 INF] ✅ Download cashbox configuration
[10:11:10 INF] ✅ Parse cashbox configuration in launcher configuration
[10:11:11 INF] ✅ Parse cashbox configuration
[10:11:11 INF] ✅ Decrypt cashbox configuration
[10:11:11 INF] ✅ Setup data protection
[10:11:11 INF] ✅ Decrypt launcher configuration
[10:11:11 INF] ✅ Setup monarch services
[10:11:11 INF] ✅ Setup monarch ProcessHostService
[10:11:11 INF] ✅ Build monarch WebApplication
[10:11:11 INF] ✅ Start monarch WebApplication
[10:11:11 INF] ✅ Start plebian processhostservice client
[10:11:11 INF] ✅ Setup plebian services
[10:11:11 INF] ✅ Build plebian Host
[10:11:11 INF] ✅ Start plebian Host
[10:11:11 INF] ✅ Shutdown launcher gracefully
[10:11:11 INF] Doctor found no issues.
The Launcher 2.0 can be installed as a service on Windows and Linux (when systemd is available) using the install command:
fiskaltrust.Launcher.exe install --cashbox-id <cashboxid> --access-token <accesstoken> --launcher-configuration-file <launcher-configuration-file>The Launcher 2.0 can update itself automatically. For this the launcherVersion must be set in the launcher configuration file.
This can be set to a specific version (e.g. "launcherVersion": "2.0.0-preview3" updates to version 2.0.0-preview3 ).
Or this can be set to a SemVer Range (e.g. "launcherVersion": ">= 2.0.0-preview3 < 2.0.0" automatically updates to all preview versions greater or equal to 2.0.0-preview3 but does not update to non preview versions).
Clone this GitHub repository and build the project with Visual Studio.
When using VS Code, please ensure that the following command line parameters are passed to dotnet build to enable seamless debugging: -p:PublishSingleFile=true -p:PublishReadyToRun=true .
Q: Are additional components required to be installed to be able to run the Launcher 2.0?
A: The Launcher 2.0 does not require any additional components to be installed.
Q: Which market can test the launcher 2.0?
A: Right now only the German and Italian market can test the launcher 2.0. It is possible for everyone to register to the German/Italian sandbox and test the launcher 2.0. Also, we are working on making the launcher available for all markets.
Q: Is it possible to update the launcher version (e.g. from 1.3 to 2.0)?
A: It is possible to switch the launcher version from 1.3 to 2.0 using the version Launcher 2.0.0-rc.3 and later versions.
Q: Can I use port sharing to run multiple Queues or SCUs on the same port (e.g. rest://localhost:1500/queue1 and rest://localhost:1500/queue2 )
A: Yes this is possible by setting the launcher config parameter useHttpSysBinding to true.
HttpSysBinding has some limitations:
- It is only supported on windows
- It is not supported for GRPC communication
- The launcher may need to be run as an administrator
- No TLS certificates can be set
- The Launcher has access problems when writing to the keyring on Linux if run as a service.
The launcher configuration parameter
useLegacyDataProtectionneeds to be set totrueas a workaround. (#100
We welcome all kinds of contributions and feedback, e.g. via issues or pull requests, and want to thank every future contributors in advance!
Please check out the contribution guidelines for more detailed information about how to proceed.
The fiskaltrust Middleware is released under the EUPL 1.2.
As a Compliance-as-a-Service provider, the security and authenticity of the products installed on our users' endpoints is essential to us. To ensure that only peer-reviewed binaries are distributed by maintainers, fiskaltrust explicitly reserves the sole right to use the brand name "fiskaltrust Middleware" (and the brand names of related products and services) for the software provided here as open source - regardless of the spelling or abbreviation, as long as conclusions can be drawn about the original product name.
The fiskaltrust Middleware (and related products and services) as contained in these repositories may therefore only be used in the form of binaries signed by fiskaltrust.