How it works
1. Generate your pipeline
Your team enters the details of each environment (dev, test, pre-prod, prod): hostnames, Register endpoints, brand and software product IDs, certificate subjects, token lifetimes, image tags and replica counts. The site generates one parameter file per environment, inheriting from a base file, and a pipeline with these stages. Ping Identity's recommended DevOps approach is the default; other toolchains are available on request.
Mirror
Copies the Ping container images, pinned by digest, into the bank's own registry.
Build
Builds the bank's images with a software bill of materials and an image scan.
Configure
Checks every environment parameter and plans the infrastructure and Ping configuration changes.
Deploy
Deploys the Ping CDR Kit with the Ping Helm chart; secrets are read from Vault or OpenBao at run time.
Test
Runs Consumer Data Standards flows against the ACCC mock Register and mock data recipient, and the OpenID FAPI tests.
Security
Scans for secrets, image vulnerabilities, manifest errors and TLS ciphers.
Promote
Promotes the same images and configuration to the next environment after approval.
Certificate rotation
Watches certificate expiry, generates keys and signing requests, and installs issued certificates.
Register sync check
Alerts when Register status data is older than the five minutes the standards allow.
2. Work through on-boarding
Each step has a status, an owner and evidence. Steps that need a running environment link to the pipeline stage they depend on: the Conformance Test Suite needs an environment deployed with Register CA certificates, and activation needs production deployed with the production certificate.
Data Holder
1. Participant Portal access
Create the Participant Portal account, with an initial primary business contact listed on the ABR or ASIC record, and delegate the contact roles.
Owner: Bank · Source: Participant Portal User Guide v23, sections 3 and 5; on-boarding guide v3, section 2
2. Registration as a data holder
Submit the data holder registration in the Participant Portal.
Owner: Bank · Source: Participant Portal User Guide v23, section 6.1; on-boarding guide v3, section 1.4
3. On-boarding preparation
Accept the Subscriber Agreement and Relying Party Agreement, enter participation and brand details, and accept the CDR Trade Mark Licence Agreement to use the CDR logo.
Owner: Bank, ID Partners · Source: On-boarding guide v3, steps 1–3 and Appendix D
4. Public Key Infrastructure
Request the test and production certificates from the CDR Register CA with certificate signing requests in the format the standards set.
Owner: Bank, ACCC · Source: On-boarding guide v3, steps 5 and 9; Consumer Data Standards, Certificate Management
5. Conformance Test Suite
Enrol in the Conformance Test Suite, nominate an authorised CTS tester, connect the test environment and pass the assigned test plan.
Owner: Bank, ID Partners, ACCC · Source: On-boarding guide v3, steps 4, 6 and 7; CTS Data Holder technical guidance 5.3.0
6. Activation on the CDR Register
Provide production details, confirm production readiness and receive Registrar activation.
Owner: Bank, ACCC · Source: On-boarding guide v3, steps 8, 10 and 11
7. Post-activation obligations
Run Get Metrics, Status and Outages, respond to Register status changes, rotate certificates and submit reports under rule 9.4 by 30 January and 30 July.
Owner: Bank, ID Partners · Source: Consumer Data Standards, Admin APIs and Metadata Cache Management; CDR Rules 9.3 and 9.4
Accredited Data Recipient
1. Participant Portal access
Create the Participant Portal account and delegate the contact roles.
Owner: Bank · Source: Participant Portal User Guide v23, sections 3 and 5
2. Accreditation
Apply for unrestricted or sponsored accreditation with evidence for information security, dispute resolution and insurance.
Owner: Bank, ID Partners, ACCC · Source: CDR Rules 5.2, 5.5 and 5.12 and Schedule 2; Accreditation Guidelines version 6
3. On-boarding preparation
Enter brand and software product details in the Participant Portal.
Owner: Bank · Source: On-boarding guide v3, step 3
4. Public Key Infrastructure
Request the client certificates that secure calls to the Register and to data holders.
Owner: Bank, ACCC · Source: Consumer Data Standards, Certificate Management; Participant Portal User Guide v23, section 10.7
5. Conformance Test Suite
Pass the CTS competencies for each software product: Dynamic Client Registration, establishing consent, and arrangement revocation in both directions.
Owner: Bank, ID Partners, ACCC · Source: CTS Accredited Data Recipient technical guidance 4.5.0
6. Activation on the CDR Register
Provide production details, confirm readiness and receive activation, then perform Dynamic Client Registration with data holders.
Owner: Bank, ACCC · Source: On-boarding guide v3, steps 8, 10 and 11
7. Post-activation obligations
Keep the consumer dashboard, records and controls assessment current and submit reports under rule 9.4.
Owner: Bank, ID Partners · Source: CDR Rules 1.14, 9.3, 9.4 and Schedule 2