LoginUrl settings on Single Sign On Settings or Oauth configurations updated to be instanceless for CS instances on Spring'20
Last updated 25 days ago ·Reference W-7809460 ·Reported By 16 users
In Spring '20 sandboxes, SAML logins are prematurely expecting the ACS URL to use a stabilized, instance-less My Domain hostname, regardless of whether the org had activated the "Stabilize the Hostname for My Domain URLs in Sandboxes" critical update.
Errors such as "Failed to get Next element" may have also been seen in API tools such as workbench, Dataloader, and dataloader.io
This issue began on Spring '20 sandboxes at 2020-07-11:00:00:00Z (UTC) or 2020-07-10 at 5:00 PM PD
In a spring sandbox without the critical update "Stabilize the Hostname for My Domain URLs in Sandboxes", attempt to login to dataloader via Oauth or Password authentication
The workaround is to activate the "Stabilize the Hostname for My Domain URLs in Sandboxes" critical update in their affected Spring '20 sandboxes. In some instances you will also need to update the SAML ACS URL for those sandboxes in their SAML identity providers (IdP) to use the instance-less hostnames.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.