A legacy SAML provider caused authentication issues for an enterprise-grade AWS infrastructure.A critical KMS key was inaccessible due to lack of permission to update the key policy.A role from a previous SSO solution was discovered with full permissions on the KMS key.A new SAML provider was hijacked to regain access and update the KMS key policy.