# SignUp to Regular Web App

**URL:** <https://community.auth0.com/t/signup-to-regular-web-app/43896>\
**Category:** Get Help\
**Created:** [June 1, 2020, 2:13pm UTC](https://community.auth0.com/t/signup-to-regular-web-app/43896 "2020-06-01T14:13:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![luke1988](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/luke1988/32/13158_2.png) [@luke1988](https://community.auth0.com/u/luke1988)\
**Post date:** [June 1, 2020, 2:13pm UTC](https://community.auth0.com/t/signup-to-regular-web-app/43896/1 "2020-06-01T14:13:32Z")

</div>

Hi guys,

I have a product web site where I host custom signup form using Auth0.js. This is my custom JS on top of your Auth0.js:

```
var webAuth = new auth0.WebAuth({
    domain: 'auth.XXXX.com',
    clientID: 'Yn1lr ..............',
    responseType: 'token',
    redirectUri: 'https://app.XXXXX.com/continue'
  });
 
function doSignUp() {
    .... 
    webAuth.redirect.signupAndLogin({
         connection: databaseConnection,
         email: email,
         password: password,

```

After successfull signup, user is redirected into app at `https://app.XXXXXX.com` which is Angular SPA and uses your Auth0 SDK for SPA. So far so good, works great!

Here comes the tricky part.

I have another web site (`connect-shopify.XXXXXX.com`) for integration with [Shopify.com](http://Shopify.com) where I want to ask user to either use existing account or create new. Screen has a button [Use existing account] or embedded SignUp form which is very same as code above but differs in responseType and clientID:

```
var webAuth = new auth0.WebAuth({
    domain: 'auth.XXXX.com',
    clientID: '78Gde4 ..............',
    responseType: 'code',
    redirectUri: 'https://connect-shopify.XXXXX.com/auth/callback'
  });
 
      webAuth.redirect.signupAndLogin({
         connection: databaseConnection,
         email: email,
         password: password,

```

Both web sites are built with .NET Core 3.1 and this one (connect-shopify) has been implemented using your wonderfull Quickstart guide for Regular Web App

Button [Use existing account] works also great, redirects user to Auth0 login page, and after successfull login, and after some redirects user ends at `connect-shopify.XXXXXX.com/continue` where is the rest of integration process flow. Great!

However, SignUp does not work. I end up with this response:

```
Now listening on: http://[::]:8080
Application started. Press Ctrl+C to shut down.
fail: Microsoft.AspNetCore.Server.Kestrel[13]
      Connection id "0HM0668TOF4O8", Request id "0HM0668TOF4O8:00000001": An unhandled exception was thrown by the application.
System.Exception: An error was encountered while handling the remote login.
 ---> System.Exception: Unable to unprotect the message.State.
   --- End of inner exception stack trace ---
   at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1.HandleRequestAsync()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)

```

What could be wrong? [ASP.NET](http://ASP.NET) is set-up exactly according to your Quickstart docu, copy/paste code.

Thanks

---

<div class="post-metadata">

**Author:** ![Scheffler](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/scheffler/32/24476_2.png) [@Scheffler](https://community.auth0.com/u/Scheffler)\
**Post date:** [September 25, 2020, 1:19pm UTC](https://community.auth0.com/t/signup-to-regular-web-app/43896/2 "2020-09-25T13:19:05Z")

</div>

I’m receiving the same error and having trouble finding much info.

---

<div class="post-metadata">

**Author:** ![rsanchez1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rsanchez1/32/24882_2.png) [@rsanchez1](https://community.auth0.com/u/rsanchez1)\
**Post date:** [January 6, 2021, 5:26pm UTC](https://community.auth0.com/t/signup-to-regular-web-app/43896/3 "2021-01-06T17:26:23Z")

</div>

So, this is 4 months old, and nobody has replied to you it seems… Were you or anyone able to resolve this issue? I am having a similar issue on my app.