# Login with Twitter - Second modal?

**URL:** <https://community.auth0.com/t/login-with-twitter-second-modal/130661>\
**Category:** Get Help\
**Tags:** login-experience, new-universal-login-experience\
**Created:** [March 27, 2024, 8:27pm UTC](https://community.auth0.com/t/login-with-twitter-second-modal/130661 "2024-03-27T20:27:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![claudio.villalobos](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/claudio.villalobos/32/55950_2.png) [@claudio.villalobos](https://community.auth0.com/u/claudio.villalobos)\
**Post date:** [March 27, 2024, 8:27pm UTC](https://community.auth0.com/t/login-with-twitter-second-modal/130661/1 "2024-03-27T20:27:46Z")

</div>

Hello,

I am using `@auth0/auth0-react` to login on my webapp with Twitter.

```auto
// Using this: 
loginWithRedirect: (
    options?: RedirectLoginOptions<AppState>
  ) => Promise<void>;

// With these autorization params: 
 {
  audience: `https://.../api/v2/`,
  redirect_uri: window.location.origin,
  scope:
    "openid email profile read:current_user update:current_user_identities",
  connection: "twitter",
};

```

Everything works fine but when a new user logs in (and in consequence creates the profile on auth0), two steps are required to complete the signup.

I am wondering if there is a way to avoid having the user go through these two steps.

After pressing login, first the user sees the following page:

 ![image](https://global.discourse-cdn.com/auth0/original/3X/5/8/58023533ddd143338845ac80d52b5af4c7a19894.jpeg)

After logging in with Twitter, the user is presented the following page:

 ![image](https://global.discourse-cdn.com/auth0/original/3X/0/3/0340daf5d7d5f13b8c3fe1bfd9415e99ac195798.jpeg)

Is it possible? if the account is being created, I don’t understand why the need for the second modal.

Thanks,  
Claudio

---

<div class="post-metadata">

**Author:** ![dawid.matuszczyk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dawid.matuszczyk/32/74550_2.png) [@dawid.matuszczyk](https://community.auth0.com/u/dawid.matuszczyk)\
**Post date:** [March 29, 2024, 1:15am UTC](https://community.auth0.com/t/login-with-twitter-second-modal/130661/2 "2024-03-29T01:15:00Z")

</div>

Hi @claudio.villalobos

Welcome to the Auth0 Community!

Thank you for posting your question, if you are testing your app on localhost you are not able to skip consent.

> As `localhost` is never a verifiable first-party (because any malicious application may run on `localhost` for a user), Auth0 will always display the consent dialog for applications running on `localhost` regardless of whether they are marked as first-party applications. During development, you can work around this by modifying your `/etc/hosts` file to add an entry such as the following:
> 
> `127.0.0.1 myapp.example`

[https://auth0.com/docs/get-started/applications/confidential-and-public-applications/user-consent-and-third-party-applications#skip-consent-for-first-party-applications](https://auth0.com/docs/get-started/applications/confidential-and-public-applications/user-consent-and-third-party-applications#skip-consent-for-first-party-applications)

I should be normal once you deploy it. I hope this will help you!

Thanks  
Dawid

---

<div class="post-metadata">

**Author:** ![claudio.villalobos](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/claudio.villalobos/32/55950_2.png) [@claudio.villalobos](https://community.auth0.com/u/claudio.villalobos)\
**Post date:** [April 1, 2024, 7:07pm UTC](https://community.auth0.com/t/login-with-twitter-second-modal/130661/3 "2024-04-01T19:07:15Z")

</div>

Ohhh I see. Great! Thanks for the quick response 🙂

---

<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:** [April 15, 2024, 7:07pm UTC](https://community.auth0.com/t/login-with-twitter-second-modal/130661/4 "2024-04-15T19:07:54Z")

</div>

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