refreshing sandboxes when direct login is blocked

file under stupid workarounds that cant possibly exist in a 50B platform

if you use single sign on in prod, and block login from login.salesforce.com because security and all, refreshing sandboxes becomes a stupid pita because the new sandbox inherits the ‘block login from’ setting,

therefore after refresh is complete, you click ‘login’ in the sandbox list from prod, and it takes you to the direct url to login (ie cs13.salesforce.com)

enter your pwd and you get this helpful message

Please check your username and password. If you still can’t log in, contact your Salesforce administrator.

To fix this, you have to manually craft the mydomain url for your sandbox. this is formatted as

prodMyDomain–sandboxName.sandbox.lightning.force.com

in my case, prod my domain = ashoka
sandbox name = oppasn

so the sandbox my domain url =
https://ashoka–oppasn.sandbox.lightning.force.com/

now you are not logging in from test.salesforce.com, you are logging in from mydomain url, so you can complete the login.

 
0
Kudos
 
0
Kudos

Now read this

Geocode all the Records

** RATHER UNFORTUNATE UPDATE - NOV 2018** Did some sleuthing and discovered that geocodes bug out sometimes when there is something like a room number that data.com doesnt like in the street address (even though the address is valid, the... Continue →