Users attempting to update or create secrets through specific API endpoints encountered “Access Denied” errors. This impacted the following scenarios:
Affected Endpoints:
The first two endpoints are used primarily by integrations and automation scripts. The latter two are used by the UI for list assignments and file attachments.
Start Time: November 15, 2025 6:00 PM Eastern
End Time: November 17, 2025 9:35 PM Eastern
In the latest SSC release, a bug fix was deployed introducing new logic intended to correctly apply the LauncherConnectAsSecretId parameter in cases where a privileged secret lacked a PuTTY launcher. While the intended scenario was resolved, the updated logic unintentionally caused Access Denied failures across the four endpoints listed above.
This issue was partially identified and corrected during QA; however, not all affected paths were detected. A relevant integration test existed, but the test selection logic used during merge-time impact analysis did not include that test. As a result, the problematic code path was not validated before deployment, allowing a narrower version of the issue to reach production.
The issue was resolved by reverting the affected code and redeploying the previous stable implementation.