Expense, Travel, Invoice, Request, Imaging, Analysis/Intelligence: P1

Update timeline

1. resolved Jun 26, 2025, 07:21 PM UTC

   We are working to determine the user impact and will provide information as it becomes available.

2. resolved Jun 26, 2025, 07:38 PM UTC

   In the US2 Data Center, logging in via SSO through the SAP Concur website and SAP Concur mobile app is currently unavailable. Affected users may experience login errors, stating, “Sorry, but we’re having trouble signing you in. SAML message was not properly base 64 encoded” when attempting to log in. The Incident Response Team (IRT) is currently investigating. Our next scheduled update will be in one hour or sooner should a significant change occur.

3. resolved Jun 26, 2025, 08:10 PM UTC

   In the US2 Data Center, logging in via SSO through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have experienced login errors, stating, “Sorry, but we’re having trouble signing you in. SAML message was not properly base 64 encoded” when attempting to log in. Services have returned to normal operating levels. We will continue monitoring performance for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved.

4. resolved Jun 26, 2025, 08:28 PM UTC

   In the US2 Data Center, logging in via SSO through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have experienced login errors, stating, “Sorry, but we’re having trouble signing you in. SAML message was not properly base 64 encoded” when attempting to log in. The Incident Response Team (IRT) rolled back a recent change to restore service. We have verified that service performance is stable and will now resolve the incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.

5. resolved Jul 10, 2025, 06:14 PM UTC

   In the US2 Data Center, logging in via SSO through the SAP Concur website and SAP Concur mobile app was unavailable. Affected users may have experienced login errors, stating, “Sorry, but we’re having trouble signing you in. SAML message was not properly base 64 encoded” when attempting to log in. An update deployed to the authentication workflow to migrate single sign-on services still using a legacy SAML endpoint to the current one due to a code defect that had not surfaced during testing resulted in some SSO Identity Providers returning an error and in a failed user log. The Incident Response Team deployed an update to use the encoding that was required for these Identity Providers. This resolved the issue and allowed the logins to authenticate successfully. The following corrective actions were identified: -Deployed an update to use the encoding required by some Identity Providers -Add additional tests to validate SSO response matches encoding requirements for all identity providers