Versions Compared

Version Old Version 3 New Version 4
Changes made by

Isla Humphreys

David Plews

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

This form is for information only. The information will be gather using the API Hub Service Desk

Expand
titleMENU
Table of Contents
stylenone

1.0 Purpose

This form should be used to gather and share environment specific configuration details for the LFI’s Pre-Production environment.

...

The table below sets out the steps for each certificate where the LFI holds the Transport & Signing Private keys.

...

Section

...

Certificate

...

Steps

...

Section

Certificate

Steps

Additional Information to be Supplied by LFI

Transport Client Certificate

C3

This certificate is used by Ozone to recognise the LFI when it calls the hh and cm

These steps are repeated for C3 S4 Sig3

  1. LFIto generate private key for the certificate

  2. LFI to generate CSR

  3. LFI to generate the certificate from OFTF Sandbox directory

  4. LFIto provide JWKS URL and KID

Code Block
LFI to Insert JWKS URL 
LFI to Insert KID

Transport Server Certificate

S4

The certificate is used by the LFI to identify its Ozone Connect service to API Hub.

Code Block
LFI to Insert JWKS URL 
LFI to Insert KID

Signing Certificate

Sig3

Used by the LFI to sign requests and responses sent to API Hub.

This is used to sign the jwt-auth header for:

  • Ozone Connect responses

  • hh-pub requests

  • cm-pub requests

LFI will use the public key in the JWKS to verify the signature.

Code Block
LFI to Insert JWKS URL 
LFI to Insert KID

...