function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Alberto Real 6Alberto Real 6 

"so" parameter in sso

Hi! We have configurated Single Sign On Connection in a SandBox and in Production Enviroment.

In a Sandbox, the resulting field "Login URL" in Single Sign-On Settings was:

https://xxxx--xxx.my.salesforce.com (https://santanderservice--pre.my.salesforce.com" style="color:blue; text-decoration:underline)

(WITHOUT 'so' parameter in URL)

But, in Production the "Login URL" was:

https://xxxxxxxx.my.salesforce.com?so=00D1i000000V5bf (https://santanderservice.my.salesforce.com?so=00D1i000000V5bf" style="color:blue; text-decoration:underline)

(WITH 'so' parameter in URL)

We have tested in Production with and without the 'so' parameter and runs OK.

Our question are:

- Why Sandbox and Production URLs are different about 'so' parameter?
- Can we use the URL without parameter in both cases?
- Will this change in the future?

Thanks!
cruttley2cruttley2
Did you ever figure out what the "so=" parameter is for? I am struggling with the same issue! All help appreciated.
 
Fernanda Iwamoto 8Fernanda Iwamoto 8
Also wondering why in some cases Salesforce put this parameter and others not. Didn´t find any documentation about...
I´m setting SSO for more than 10 different orgs and one of them created this param "?so=XXXXX" on Login URL. 
Fernanda Iwamoto 8Fernanda Iwamoto 8
One thing I noticed is, it is not related to the environment, because I´m on a sandbox and it put the param.