sections in the article
This issue has been resolved on the 25th of July 2022 - all necessary information from the incident has been updated below.
As the fix for the SSO problem has now gone out into production, those who used the AD workaround -(changing the sso-prod1a addre--sses) will need to revert Entity ID back to sso.productmarketingcloud.com, and Reply URL to https://sso.productmarketingcloud.com/signin-saml-[customer safename].
We apologize for the inconvenience but made the decision that the priority was to solve the problem for everyone as soon as possible.
Users that are already logged in, may experience a brief hang in the system but should keep their sessions and be able to continue to work. But in order for users to do a new login, the SSO settings need to be reverted as above.
After the maintenance window on Saturday the 23rd of July customers who use SSO for authentication may be impacted by problems logging in.
1) Change the customer side AD configuration by adding sso-prod1a-euw.productmarketingcloud.com and sso-prod1a-use.productmarketingcloud.com addresses under Basic SAML Configuration in your AD (according to the screenshot below) - this solves the situation.
2) It may also be required to update the response URL to https://sso-prod1a-[euw|use].productmarketingcloud.com/signin-saml-bco and make that the default URL.