Skip to content

feat: Update hometest supplier spec to add app-level3 auth and new integration environment - #62

Open
iichr wants to merge 1 commit into
mainfrom
feature/supplier-spec-changes-uat-publication
Open

feat: Update hometest supplier spec to add app-level3 auth and new integration environment#62
iichr wants to merge 1 commit into
mainfrom
feature/supplier-spec-changes-uat-publication

Conversation

@iichr

@iichr iichr commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Description

Update spec before publishing to UAT.

  1. Replaced the generic bearer authentication scheme with APIM's app-level3 application-restricted signed-JWT security scheme (following the example of other OASs)
  2. Documented that suppliers authenticate their application, not an end user, and linked to the NHS signed-JWT integration guide.
  3. Added the sandbox, integration and production environment table. Only the sandbox URL is currently available; integration and production remain unavailable.
  4. Corrected the sandbox documentation to state that it returns canned responses and enabled the "Try this API" feature.

Context

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@iichr
iichr requested review from a team as code owners August 4, 2026 16:32
@sonarqubecloud

sonarqubecloud Bot commented Aug 4, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant