Find your content:

Search form

You are here

Sandbox settings in Single sign on org


I created a new sandbox for my org. I am trying to activate a developer sandbox and I am struck there. All I see is a refresh link and login link. I am unable to see the activation link. I have activated SSO on prod (does that hurt me from activating my sandbox?) What are the reasons why I cannot activate my dev box ( I am sure I am not hitting the limits on number of Sandbox). Is it that SSO by default needs to be cofiugured for accessing the sandbox too?

Please advice and throw some light on this mystery of SSO and Sandbox settings

Attribution to: Rao

Possible Suggestion/Solution #1

SSO shouldn't factor into this at all. If you just created the sandbox from scratch, you will not have the option to activate; it will be ready to use as soon as it is finished copying. Activation is only necessary when refreshing an existing sandbox, where the sandbox is still available for use during the course of the copy process (and then swapped out with the fresh production copy when you choose to activate it).

Attribution to: JCD

Possible Suggestion/Solution #2

When you create a sandbox, user accounts are copied over but the usernames are changed; the usernames will have the sandbox name appended. So if you are in production, your sandbox username will be[sandbox name]. This is probably what is breaking the SSO; your SSO username likely no longer matches your sandbox's username.

Attribution to: Mike Chale
This content is remixed from stackoverflow or stackexchange. Please visit

My Block Status

My Block Content