Skip to content

ATO-2575: remove new v2 key feature flags#8371

Open
Louisasa wants to merge 3 commits into
mainfrom
ATO-2575-remove-feature-flag
Open

ATO-2575: remove new v2 key feature flags#8371
Louisasa wants to merge 3 commits into
mainfrom
ATO-2575-remove-feature-flag

Conversation

@Louisasa
Copy link
Copy Markdown
Contributor

@Louisasa Louisasa commented May 21, 2026

Wider context of change

As part of the key rotation, the new V2 keys have been successfully rotated and no longer need to be behind a feature flag.

What’s changed

Remove UseV2Key, PublishV2Key, and ProvisionV2Key feature flags, as well as tidy up fetching the old public key for non-reauth journeys.

Manual testing

Tested in dev

Checklist

  • Lambdas have correct permissions for the resources they're accessing. N/A
  • Impact on orch and auth mutual dependencies has been checked. N/A
  • Changes have been made to contract tests or not required. N/A
  • Changes have been made to the simulator or not required. N/A
  • Changes have been made to stubs or not required. N/A
  • Successfully deployed to authdev or not required.
  • Successfully run Authentication acceptance tests against sandpit or not required. N/A
  • Added new endpoints to local running (LocalOrchestrationApi.java) or not required. N/A

@Louisasa Louisasa requested review from a team as code owners May 21, 2026 16:37
if (JWSAlgorithm.RS256 == jwt.getHeader().getAlgorithm()
&& configuration.isRsaSigningAvailable()) {
if (configuration.isPublishNextExternalTokenSigningKeysEnabledV2()) {
var oldPublicKey = jwksService.getPublicTokenRsaJwkWithOpaqueId();
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made this change because I suddenly panicked about removing the old keys from the JWKs endpoint would break fetching them, but this actually gets it straight from KMS so wouldn't break, but it isn't needed anymore. Happy to remove from this PR tho as it isn't entirely related

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I lean toward thinking that's better done as BAU or with a fresh ticket.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm kind of tempted to leave it in though so it doesn't get missed. It's not entirely unrelated but I can update the commit to at least be BAU?

@Louisasa Louisasa force-pushed the ATO-2575-remove-feature-flag branch 4 times, most recently from 7a0f5c8 to a502231 Compare May 22, 2026 09:20
@Louisasa Louisasa force-pushed the ATO-2575-remove-feature-flag branch from a502231 to 2e62470 Compare May 22, 2026 10:44
@sonarqubecloud
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.

2 participants