We uncovered a gap in our Auth0 SSO for our Customers signing into our NetSuite Customer Center specifically related to our Sandbox environments.
During the Sandbox post connection validation we executed a custom NetSuite script created by the Auth0 implementers, which identified that 49 Sandbox contacts met the script criteria (entitlement to log in but did not have an Auth0 id attached to the contact record yet) & should be able to log in to our Sandbox Customer Center. That script sent those 49 Sandbox contacts to Auth0 Sandbox.
Auth0 Sandbox sent the standard ...." you have been granted access"... Sandbox emails to the 49 contacts, in error.
Some of those contacts that received the email "took it for real" and so followed the steps and ended up "replacing" their Production Customer Center access with this Sandbox access, were confused & logged tickets. (This is how we uncovered the gap.)
We investigated and found that Auth0 has no mechanism/safeguard to prevent testing email from being distributed.
We dealt with the immediate 49 contacts but are now determining how to prevent it.
The Auth0 team suggests invalidating (change the domain to @sandbox.com for example) all Sandbox contacts' email addresses in Sandbox systems after each refresh through a NetSuite script.
NetSuite prevents Sandbox emails from being sent out in settings, Email preferences as below.
Workday prevents Sandbox emails from being sent out in settings. I got this screenshot from a Workday architect and only post here for continuity of systems/business process.
I find it hard to believe that anyone is invalidating all Sandbox email addresses each time there is a refresh to accommodate a downstream system.
I suggested a custom Auth0 script to recognize the sandbox contact url (9999999-sb1…) and prevent the emails from Auth0.
Can anyone suggest an industry standard best practice for preventing emails from downstream Sandbox environments (most specifically Auth0)?
Any and all suggestions are appreciated.
Thanks all…