Some SCA Cloud access customers with specific trust configuration in their Identity webapp cannot connect AWS IAM Identity center and GCP cloud provider

Update timeline

1. investigating Nov 09, 2026, 07:59 AM UTC

   Please be aware that some customers with specific trust configuration in their Identity webapp can not connect to GCP and AWS IDC cloud provider. This is relevant for Identity as IDP and not 3rd party / OKTA and relevant only if webapp configuration in the Trust section, under 'SP' configuration, is 'Metadata'. **What happened:** Some users who tried to elevate to an AWS IAM Identity center/GCP role got "Oops! Something went wrong. Please try again in a few minutes" (error CA1040). Retrying didn't help. No access was granted. **Who was affected:** Tenants whose AWS IAM Identity center/GCP application has no SAML trust configured (SP Entity ID) in Identity. These tenants could elevate normally before this date. **Workaround:** Go to webapp config in Identity manage space : Go Trust (verify that config is initially set on 'Metadata') Service Configuration section Choose "Manual configuration" In the 'SP Entity field' -> enter any valid url (dummy) Choose again 'Metadata' and Save Thank you, Idira Secure Cloud Access

2. identified Nov 09, 2026, 08:08 AM UTC

   Hello, Root cause was identified - R&D is working on a fix. We will update shortly Thank you