Assess Impact of PROD/Sandbox Split on API Users

A UAT issue identified an API user who was unable to access Sandbox account functionality for PPR product and was being redirected to the home page. Refer to this topic in https://github.com/bcgov/api.connect/discussions/6

Initial investigation suggests the API key may have been issued prior to the PROD/Sandbox environment split and is not aligned with the current Sandbox account structure.

Users were advised to create a new Sandbox account and a new API key will be issued, but it is unclear whether this is an isolated case or if other API users were similarly affected during the PROD/Sandbox split.

**Objective**

Conduct a quick assessment to determine whether additional API users may require remediation as a result of the PROD/Sandbox split.

Tasks:

- Identify API keys issued prior to the split.
- Determine whether any active API users are still using these legacy keys.
- Assess whether similar access issues could impact other API users.
- Document findings and recommended remediation approach.

Start with the UAT scenario and discussion 6, then identify when the PROD/Sandbox split occurred and review API keys issued before it. Compare those legacy keys with active API users and assess whether they show the same Sandbox access problem. Document affected users, findings, and the recommended remediation approach.

Written by the indexing model from the issue text.