Skip to content

Conversation

@SanjayChopraNHS
Copy link
Contributor

@SanjayChopraNHS SanjayChopraNHS commented Dec 1, 2025

Overview

Jira ticket: PRMP-683

Description

We need to have some form of public key management in-place so that keys are rotated.

Context

As keys are created by the customer and supplied to us, rotation of keys is out of our control, but we can expire keys by removing them from the key store at a given age - 12 weeks being the standard, at which point we would email the customer to let them know that their key has expired and they need to provide a new key to continue using the service.

Checklist

Tasks for all changes:

  • [x ] 1. I have linked this PR to its Jira ticket.
  • 2. I have run git pre-commits. (WIP)
  • 3. I have added and/or updated relevant tests.
  • 4. I have updated relevant documentation.
  • 5. I have considered the cross-team impact (and have PR approval from both Core & Demographics if necessary).
  • 6. I have successfully deployed this change to a sandbox and witnessed unit and e2e tests passing:

@SanjayChopraNHS SanjayChopraNHS changed the title feat: Add SSH key expiry management for Transfer Family (WIP) [PRMP-683] feat: Add SSH key expiry management for Transfer Family (WIP) Dec 1, 2025
@sonarqubecloud
Copy link

@SanjayChopraNHS SanjayChopraNHS merged commit 8e4ffcb into main Dec 17, 2025
28 checks passed
@SanjayChopraNHS SanjayChopraNHS deleted the PRMP-683 branch December 17, 2025 10:48
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.

5 participants