# Invalid\_signup when email contains +test?

**URL:** <https://community.auth0.com/t/invalid-signup-when-email-contains-test/57205>\
**Category:** Get Help\
**Tags:** login, auth0\
**Created:** [February 2, 2021, 12:59pm UTC](https://community.auth0.com/t/invalid-signup-when-email-contains-test/57205 "2021-02-02T12:59:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rai1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rai1/32/13366_2.png) [@rai1](https://community.auth0.com/u/rai1)\
**Post date:** [February 2, 2021, 12:59pm UTC](https://community.auth0.com/t/invalid-signup-when-email-contains-test/57205/1 "2021-02-02T12:59:30Z")

</div>

We’ve noticed an error trying to sign up to our application using the email address “[foo.bar+test1@gmail.com](mailto:foo.bar+test1@gmail.com)”, but “[foo.bar+candidate@gmail.com](mailto:foo.bar+candidate@gmail.com)” works fine.

Why is this happening?

Is this something that we can configure for our tenant?

---

<div class="post-metadata">

**Author:** ![stephanie.chamblee](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/stephanie.chamblee/32/26087_2.png) [@stephanie.chamblee](https://community.auth0.com/u/stephanie.chamblee)\
**Post date:** [February 2, 2021, 2:08pm UTC](https://community.auth0.com/t/invalid-signup-when-email-contains-test/57205/3 "2021-02-02T14:08:17Z")

</div>

Hi @rai1,

Thanks for joining the Community!

I tested out adding [foo.bar+test1@gmail.com](mailto:foo.bar+test1@gmail.com) and [foo.bar+candidate@gmail.com](mailto:foo.bar+candidate@gmail.com) in my own tenant, and it looks like both sign-ups are successful.

To help troubleshoot this, can you look in your dashboard logs and see if there are any additional details about the error?

Thanks!

---

<div class="post-metadata">

**Author:** ![rai1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rai1/32/13366_2.png) [@rai1](https://community.auth0.com/u/rai1)\
**Post date:** [February 2, 2021, 3:08pm UTC](https://community.auth0.com/t/invalid-signup-when-email-contains-test/57205/4 "2021-02-02T15:08:19Z")

</div>

Thanks for having a look at this. Turns out that the account already existed!

The developer who was testing this was getting the error 400 (invalid\_signup) but not the error user\_exists. Wouldn’t that have been more appropriate in this instance?

---

<div class="post-metadata">

**Author:** ![stephanie.chamblee](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/stephanie.chamblee/32/26087_2.png) [@stephanie.chamblee](https://community.auth0.com/u/stephanie.chamblee)\
**Post date:** [February 2, 2021, 3:13pm UTC](https://community.auth0.com/t/invalid-signup-when-email-contains-test/57205/5 "2021-02-02T15:13:33Z")

</div>

The error will be `invalid_signup` if your tenant has the “Use a generic response in public signup API error message” setting turned on (by default it is on). This setting is located in the “Advanced” tab in your tenant settings.

A generic error message is returned in this case to help protect against username enumeration attack.

Here is more information about the response: [Auth0 Support Center](https://support.auth0.com/notifications/5d2cb6209db665000aed8695?_ga=2.36293856.1169584547.1612177227-1595415333.1607347674)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [February 17, 2021, 3:13pm UTC](https://community.auth0.com/t/invalid-signup-when-email-contains-test/57205/6 "2021-02-17T15:13:52Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
