Visitar URL original
authorisation-server/CertificateManagement at main · ConsumerDataRight/authorisation-server · GitHub
Skip to content

Latest commit

 

History

History

CertificateManagement

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

README.md

Certificate Management

Certificates play an important part in the CDR ecosystem to establish trust between participants and protect communications. DigiCert is the Certificate Authority (CA) for the CDR and the ACCC is responsible for provisioning DigiCert certificates to participants during the on-boarding process.

For more information, consult the Certificate Management section of the Consumer Data Standards.

The Authorisation Server will mimic the behaviour of a data holder's identity provider in the CDR ecosystem and therefore will use certificates in its interactions. However, the use of DigiCert for this purpose is not feasible or scalable so an alternative approach is adopted.

There are 2 areas where certificates are used within the Authorisation Server:

  • mTLS
  • TLS

mTLS

Mutual Transport Layer Security is used extensively within the CDR ecosystem. Data Recipients are provisioned client certificates and will present that certificate when interacting with a Data Holder for consumer data sharing and with the Register when discovering Data Holder Brands and request an SSA. Data Holders are issued a server certificate for their side of the interaction. All participants need to validate the certificates presented during the establishment of a mTLS session.

The server certificate used by the Authorisation Server for mTLS connections is available at mtls\mtls-server.pfx and has the password of #M0ckDataHolder#.

Certificate Authority

A self-signed Root CA has been provisioned to handle certificate provisioning and to be used in the certificate validation processes. The server certificate/s for the Authorisation Server is generated from the self-signed Root CA.

Consult the CertificateManagement section of the Mock Register for more information.

TLS

Endpoints that are not protected by mTLS are protected by TLS. The server certificate used for TLS communication can be provisioned by the CDR CA, or alternatively participants can used a trusted third party CA.

For the Authorisation Server, a self-signed TLS certificate is used. The self-signed certificate will be issued by the Mock CDR CA, like the mTLS certificates are.

The TLS certificate for the Authorisation Server is available at tls\tls-server.pfx and has the password of #M0ckDataHolder#.