Skip to main content

Non-Production configuration

Configuration details for non-production environments

Wych non-production Data Holder Testing consists on 3 images:

Each of these service can be retrieved from the Wych Public container registry. To access this registery you we require credentials. These credentials are available in the service service portal or from you account manager.

The Wych Container Registry (WCR) stores and manages private container images and other artifacts, similar to the way Docker Hub stores public Docker container images. You can use the Docker command-line interface (Docker CLI) to login and pull images from WCR.

Overview #

Tester service is 1:1 with a Data Holder but Register and Register Auth can be shared.

flowchart LR; TEST --> DH1 DH1[Data Holder] --> REG[CDR Register] subgraph Database RDB[(Tester DB)] ADB[(Tester DB)] TDB[(Tester DB)] end subgraph Testing REG[Register] --> RDB[(Register DB)] AUTH[Register Auth] --> ADB[(Auth DB)] TEST[Tester] --> TDB[(Tester DB)] TEST[Tester] --configures--> RDB end

Log in to WCR #

Docker CLI - You must also have Docker installed locally. Docker provides packages that easily configure Docker on any Linux, macOS, or Windows system.

For best practice to manage login credentials, see the docker login command reference:

docker login wychaustralia.azurecr.io

A success login with show Login Succeeded once completed.

It is advisable to proxy the request against the WCR, this ensures you don’t have to share the registy credentials with multiple people and you can also scan the images for vulnerabilities before they enter your environment. This approach should be the same for other public repositories such as docker hub or quay.io.

AU Register Auth #

Lets start by pulling on the AU Register Auth. This service is represents provides the security, infosec, token and key, capabilities of the Register this version has been designed to support Data Holder testing and can be shared by multiple Data Holder and Tester instances but has a 1:1 relationship with the AU register.

Pull the au-register-kc image #

For more information about see au-register-kc, including versions, changelog and configuration parameters.

docker pull wychaustralia.azurecr.io/au-register-kc:[version]

The deploy location of this service (the URL) is a required parameter for the Register service.

AU Register #

Next we will pull the AU register service. This service is represents the ACCC’s AU register service, this version has been designed to support Data Holder testing and so while on an API level it is similar to the ACCC’s service it is fundamentally different in a number of key ways.

Pull the au-register image #

For more information about see au-register, including versions, changelog and configuration parameters.

docker pull wychaustralia.azurecr.io/au-register:[version]

AU Data Holder Tester #

Last service to pull requires the others to be ready, this is the Tester. This service is responsible for running the test scenarios and reporting the results of the audit.

Pull the au-register image #

For more information about see au-dataholder-tester, including versions, changelog and configuration parameters.

docker pull wychaustralia.azurecr.io/au-dataholder-tester:[version]

AU Data Holder Testing

2 mins
This Wych Data Holder Tester (Tester) is the Wych probe for validating the state of a Data Holder solution, this has been designed to support Data Holder testing for ACCC CDR standards with each test verifying a rule as set out in the specifications. graph BT; DH[Data Holder] -- REG[CDR Register] DR[Data Holder Tester] -- REG DR -- DH Tester can share a Register and Register Auth instance but has a one-to-one relationship with a Data Holder.