+ Start a Discussion
Administrator 167Administrator 167 

SSO with client

Hello everybody,

Since 15th of July, SSO on UAT is unavailable for my client. I checked the configuration and could discover that:
1) My Domain > Authentication Configuration had been kind of reset to default
2) the url sent to the client has been modified: Server Instance is no more available in the URL. HEre is the log on client side:

The request specified an Assertion Consumer Service URL 'https://xxxxxxxxx--uat.my.salesforce.com/?so=xxxxxxxxxxx' that is not configured on the relying party 'https://xxxxxxxxx--uat.CSXXX.my.salesforce.com'.
Assertion Consumer Service URL: https://xxxxxxxxxxx--uat.my.salesforce.com/?so=xxxxxxxxxxxxx
Relying party: https://xxxxxxxxxxx--uat.CSXXX.my.salesforce.com

Actually Assertion 'https://xxxxxxxxxx--uat.my.salesforce.com/?so=xxxxxxxxxxxxxx' is unknown since the one configured includes ".CSXXX" mentioned in the URL : https://xxxxxxxxx--UAT.CSXXX.my.salesforce.com?so=xxxxxxxxxxxxxx

Has anyone an idea how this configuration, including salesforce instance, could be modified without any action from an admin?
Has anyone an idea where in the configuration I can modify and correct this url to be sent to the client ?

Thank you
 
Best Answer chosen by Administrator 167
AnudeepAnudeep (Salesforce Developers) 
It is most likely because of the critical update Remove instance name from URL for sandboxes. This was auto enforced in Summer'20

I recommend contacting support if you have any specific questions around this

Anudeep

All Answers

AnudeepAnudeep (Salesforce Developers) 
It is most likely because of the critical update Remove instance name from URL for sandboxes. This was auto enforced in Summer'20

I recommend contacting support if you have any specific questions around this

Anudeep
This was selected as the best answer
cruttley2cruttley2
DO you know what is the ?so= parameter for on the URL? I am struggling with setting up SSO and understanding that parameter would help me. All help appreciated!