As we configure a new space (cloud, enterprise) for user-authentication, it often takes several iterations to get the SSO configuration right.
In our current instance, we have authentication working, but we don’t have firstName/lastName mapped properly, so user-names look like “Null, Null”.
The thing is, those names only “come in” to Retool on the first login attempt. If we do reconfigure the SSO settings and then finally “get it right” we can’t test the same username again; that user is already active and configured (incorrectly).
We tried the gmail approach of username+randomsuffix@domain.tld which works fine on the Google side, but Retool still sees it as username@domain.tld which is already set-in-stone, so to speak.
And we haven’t found any facility for “reset/delete/obliterate” an existing user to allow for iterative testing, without cluttering up the user-list. Do we need to make fake email address accounts for further testing?
I’m hoping there’s something we missed… 