- Notes, cautions, and warnings
- Introduction
- Requirements
- Download the software
- Verify the installation package
- Installation
- Uninstall Trusted Device
- Features
- Interoperability
- Run the BIOS Verification agent
- Results, troubleshooting, and remediation
The Client Registry Generator builds the required registry files using the appsettings.json file and certificates and writes them to the Docker console. The Client Registry Generator requires the following:
The following table describes variables that are used with the Client Registry Generator.
Variable | Description |
---|---|
-b, --baseUri | This variable represents the Event Repository IP address or Hostname followed by the Docker host listening port. For example,
example.server.com:31235
NOTE: This port must be the Docker host listening port or client registration fails.
|
Dell.TrustedDevice.EventsRepository.GenerateRegistry.dll | This string invokes the Client Registry Generator in the Event Repository container. |
dellemc/dtd-event-repository | This string defines the container image to use for this container.
NOTE: If a specific version of the Event Repository image is required, append this command with
:<version number>. For example:
dellemc/dtd-event-repository:1.0.2.0
|
-p, --pathToPublicCert | This variable specifies the file path of the PEM-enconded public certificate.
NOTE: This file path must include the certificate name and extension.
|
-r, --repository | This variable specifies the name of the Event Repository. |
--tty=false | To write the client registry file to a specific location, use this option. |
-v | This parameter specifies the volume to mount. |
docker compose run -v c:\example\certs:/app/certs -v c:\example\appsettings.json:/app/appsettings.json dellemc/dtd-event-repository Dell.TrustedDevice.EventsRepository.GenerateRegistry.dll --baseUri https://example.server.com:31235 -r <event repository name> -p /app/certs/ExamplePublicCertName.pem