Submit an idea and make Sauce Labs even better!
This would be helpful for accounts associated with CI servers
Understood. Multiple accounts sharing an email will not be supported as your email is used as secondary means to uniquely identify the user for password reset process. Further, enabling users to self verify emails is in contradiction to some of our customers' compliance requirements. The best we can do is to serve you via our support channels. Hopefully the addition of such new users does not become a scalable transaction.
That's what we do today and it is fine for a few users here and there. It's quite a bit of toil at scale, hence the request to allow multiple accounts to share an email or distinguish between namesake accounts and service accounts when enforcing the 1 email 1 account rule.
Sauce support can verify any email address for you. Just let us know which one and we'll verify it for you.
Here's my exchange with Sauce Labs support on this topic:
That request is quite a bit different and the proposed solution won’t work for us (and I venture to say most corporations not using gmail) as I believe the dan+Jenkins@domain.com doesn’t work on Exchange or other mail providers (at least that I know of). So, in effect, all those +xyz emails are still bogus for non-gmail mail providers and thus can’t be verified, which brings me back to my enhancement request: give the org admin the option to verify such service account emails (e.g. those with +Jenkins bogus emails).
One implementation on your side to resolve this issue would be to truncate anything after the + sign before sending out the verification email and generate a token in the subject or body that correlates the truncated email back to its +xyz version on Sauce’s side. This would allow use to have a single valid email to verify any service account that we associate with that base email address name:
In the subject or body would be a token (like you use to capture responses to your support questions) that correlates it back to the + version that sent the verification.
From Sauce Labs support:
Our Product Manager has reviewed a similar request to allow user accounts without an email address. However, it is not feasible because that is a compliance requirement from our enterprise customers. Here is the response from the Product Manager:
In the Sauce System users have to have a valid email address, That is a compliance requirement from our enterprise customers. There is a way to enable machines (ex.: Jenkins) a user. You can add a user manually from SauceLabs. You want to use a valid user email (such as firstname.lastname@example.org), but tweak it with a suffix (dan+Jenkins@domain.com). This way, for Sauce it's a different email address, but for you, the user dan can verify the user when they receive the email.
Hi Amir, that mitigation only works for customers of gsuite as most other email servers (e.g. Exchange) don't support that "extension". It's a great feature gmail/gsuite offer, but not widely supported to my knowledge. In other words, your mitigation is not a viable one for users of non-gmail/gsuite email servers.
Hello and thank you for the submission.
I hope this addresses the gap. I will set the idea status to "Already Exist" as the functionality is supported. Feel free to add comments here or connect to our support team if you wish to discuss further.
You won't be notified about changes to this idea.