Skip to content

NRF2-706 Add service-to-service API keys to the stack#2

Open
muthukswamy wants to merge 2 commits into
mainfrom
NRF2-706-service-security
Open

NRF2-706 Add service-to-service API keys to the stack#2
muthukswamy wants to merge 2 commits into
mainfrom
NRF2-706-service-security

Conversation

@muthukswamy
Copy link
Copy Markdown
Contributor

@muthukswamy muthukswamy commented May 20, 2026

Summary

Parent-repo glue for the NRF2-706 service-to-service authentication change. Wires the API keys into the Tilt compose stack and bumps the submodule pointers.

Changes

  • compose.yml — adds BACKEND_API_KEY and IMPACT_ASSESSOR_API_KEY to the backend, frontend and impact-assessor services (local dev values).
  • Bumps backend, frontend, impact-assessor and journey-tests submodule pointers to the NRF2-706 commits.

Test plan

  • tilt up — full stack healthy
  • curl http://localhost:3001/quotes/NRF-000001 → 401; with x-api-key → 200/404
  • curl -X POST http://localhost:8085/check-boundary → 401
  • Full quote journey at http://localhost:3010 — no 401s

Deployment

Real BACKEND_API_KEY / IMPACT_ASSESSOR_API_KEY values must be added per environment in cdp-tenant-config before the service PRs are deployed. The local-dev values here are placeholders only.

Related PRs

Wire BACKEND_API_KEY and IMPACT_ASSESSOR_API_KEY into compose.yml and
bump submodule pointers for the new service-to-service API key
authentication across backend, frontend and impact-assessor.
Update submodule pointers to include the package-lock.json
reconciliation in nrf-backend and nrf-frontend.
@jonnywyatt
Copy link
Copy Markdown
Contributor

jonnywyatt commented May 21, 2026

The PR description mentions an update to cdp-tenant-config - wouldn't the API keys be new secrets though?

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