We have the same issue with Customers and their upgrade sandbox: they can’t log in to the sandbox because of Active Directory.
They are using Active Directory in their production environment, but this doesn’t work in their sandbox.
All of their notifications, approval maps, etc are tied to their employee id’s that are linked to their AD user accounts.
How do we get them into the sandbox?
Hi,
Some of our customers (also in SAAS) use SSO with Active Directory. Whenever they need to go through important upgrades then we get sandboxes and we need to go through the same steps we performed to define SSO to the production instance. So, I defined the sandbox site as an application in AD and then modified the web.config of the sandbox site accordingly.
The difference is that if the sandbox is a copy of the production site, then the role mappings and the domain users are already in the sandbox.
If the sandbox is in SAAS , then I work with the SAAS team and pass them all the details for the web.config update.