# Universal Login (node-auth0 WebAuth): Where did allowedConnections go?

**URL:** <https://community.auth0.com/t/universal-login-node-auth0-webauth-where-did-allowedconnections-go/11480>\
**Category:** Get Help\
**Created:** [May 9, 2018, 11:34pm UTC](https://community.auth0.com/t/universal-login-node-auth0-webauth-where-did-allowedconnections-go/11480 "2018-05-09T23:34:04Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![bebbi](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/bebbi/32/10625_2.png) [@bebbi](https://community.auth0.com/u/bebbi)\
**Post date:** [May 9, 2018, 11:34pm UTC](https://community.auth0.com/t/universal-login-node-auth0-webauth-where-did-allowedconnections-go/11480/1 "2018-05-09T23:34:04Z")

</div>

I was using Lock before, now I don’t know how to limit the login options presented to users when using universal login. I didn’t find anything on google, so asking here.  
Thanks!

---

<div class="post-metadata">

**Author:** ![luis.rudge](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/luis.rudge/32/7073_2.png) [@luis.rudge](https://community.auth0.com/u/luis.rudge)\
**Post date:** [May 10, 2018, 1:16am UTC](https://community.auth0.com/t/universal-login-node-auth0-webauth-where-did-allowedconnections-go/11480/2 "2018-05-10T01:16:39Z")

</div>

You can set the `allowedConnections` property in the universal login page template in the [dashboard](https://manage.auth0.com/#/login_page)

---

<div class="post-metadata">

**Author:** ![bebbi](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/bebbi/32/10625_2.png) [@bebbi](https://community.auth0.com/u/bebbi)\
**Post date:** [June 14, 2018, 9:08am UTC](https://community.auth0.com/t/universal-login-node-auth0-webauth-where-did-allowedconnections-go/11480/3 "2018-06-14T09:08:39Z")

</div>

Thanks @luis.rudge.  
How can you set that dynamically, i.e. at app run time?  
I have a stripeConnect connection, which shouldn’t be presented at page login time, but later, when a logged in user wants to connect their stripe account.

---

<div class="post-metadata">

**Author:** ![luis.rudge](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/luis.rudge/32/7073_2.png) [@luis.rudge](https://community.auth0.com/u/luis.rudge)\
**Post date:** [June 14, 2018, 10:19pm UTC](https://community.auth0.com/t/universal-login-node-auth0-webauth-where-did-allowedconnections-go/11480/4 "2018-06-14T22:19:53Z")

</div>

You can customize your Universal Login Page to have any behavior you want. By default, our template will match anything you send in the `connection` param and put it inside the allowedConnections option:

```plaintext
    var lock = new Auth0Lock(config.clientID, config.auth0Domain, {
      configurationBaseUrl: 'https://cdn.auth0.com/',
      auth: {
        sso:true,
        redirectUrl: config.callbackURL,
        responseType: (config.internalOptions || {}).response_type ||
          config.callbackOnLocationHash ? 'token' : 'code',
        params: config.internalOptions
      },
      assetsUrl: config.assetsUrl,
      allowedConnections: connection ? [connection] : null,
      rememberLastLogin: true,
      language: language,
      languageDictionary: languageDictionary,
      theme: {
        //logo: 'YOUR LOGO HERE',
        //primaryColor: 'green'
      },
      prefill: loginHint ? { email: loginHint, username: loginHint } : null,
      closable: false,
      // uncomment if you want small buttons for social providers
      // socialButtonStyle: 'small'
    });

```

> **[Auth0 Universal Login](https://auth0.com/docs/authenticate/login/auth0-universal-login)**
>
> Describes how Auth0 Universal Login provides you with the means to prove your users' identities with our authorization server.

---

<div class="post-metadata">

**Author:** ![bebbi](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/bebbi/32/10625_2.png) [@bebbi](https://community.auth0.com/u/bebbi)\
**Post date:** [June 15, 2018, 7:45am UTC](https://community.auth0.com/t/universal-login-node-auth0-webauth-where-did-allowedconnections-go/11480/6 "2018-06-15T07:45:42Z")

</div>

@luis.rudge Thanks!

Nice, I got the part of Auth0Lock being called internally and customizable via Universal Login dashboard.

Now, what doesn’t work is passing variables like ‘connection’ to it from `WebAuth`:

```
new auth0.WebAuth({
…
connection: ‘stripeConnect’
})

```

didn’t seem to do the trick to limit the login options to just stripeConnect.  
I debugged the call to Auth0Lock but didn’t see any place where that connection param was passed to Auth0Lock.

If that worked, I assume for my other case of limiting to multiple connections, I can just tweak the Universal Login script to not turn connection into an array and pass:

```
connection: [‘google-oauth2’, ‘Username-Password-Authentication’]

```

---

<div class="post-metadata">

**Author:** ![luis.rudge](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/luis.rudge/32/7073_2.png) [@luis.rudge](https://community.auth0.com/u/luis.rudge)\
**Post date:** [June 15, 2018, 2:09pm UTC](https://community.auth0.com/t/universal-login-node-auth0-webauth-where-did-allowedconnections-go/11480/7 "2018-06-15T14:09:08Z")

</div>

```auto
webauth.authorize({connection: 'stripeConnect'});

```

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [December 14, 2018, 3:29pm UTC](https://community.auth0.com/t/universal-login-node-auth0-webauth-where-did-allowedconnections-go/11480/8 "2018-12-14T15:29:57Z")

</div>


