# Force a Specific Enterprise Connection ID for New Universal Login

**URL:** <https://community.auth0.com/t/force-a-specific-enterprise-connection-id-for-new-universal-login/100567>\
**Category:** Get Help\
**Tags:** login-prompt-new-experience, login-experience\
**Created:** [February 15, 2023, 2:59pm UTC](https://community.auth0.com/t/force-a-specific-enterprise-connection-id-for-new-universal-login/100567 "2023-02-15T14:59:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![matt.scachette](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/matt.scachette/32/33197_2.png) [@matt.scachette](https://community.auth0.com/u/matt.scachette)\
**Post date:** [February 15, 2023, 2:59pm UTC](https://community.auth0.com/t/force-a-specific-enterprise-connection-id-for-new-universal-login/100567/1 "2023-02-15T14:59:54Z")

</div>

Hello,

We currently are using the New Universal Login experience and a combination of several Enterprise Connections (using Identifier first) and local Auth0 accounts using databases.

Today, if a user specifies an email domain which is attached to a connection, Auth0 recognizes the domain and automatically redirects to that connection. Great, this gets us half way there.

Question. For some of our “tenants” we have several email address domains ([gmail.com](http://gmail.com), [yahoo.com](http://yahoo.com), etc) which prevent us from using identifier first for tenants which must use one specific connection 100% of the time.

Is there a way to pass in an additional parameter in our OIDC request to force a specific connnection to be utilized automatically? We also have a React client which would need to do the same thing.

Basically, something like this:

if user is attempting to access a resource tenant a, redirect anonymous user to Auth0 and force Connnection “sample-connection-adfs” to authenticate the user in all cases.

if any other tenant, follow the normal Auth0 flow by showing a username/password prompt.

Ideally, we don’t want end users of any tenant to be able to see a list of customers or organizations and we don’t want to show all of our connections. We would like to make this determination programmatically depending on the tenant configuration.

Thanks.

---

<div class="post-metadata">

**Author:** ![matt.scachette](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/matt.scachette/32/33197_2.png) [@matt.scachette](https://community.auth0.com/u/matt.scachette)\
**Post date:** [February 16, 2023, 2:16pm UTC](https://community.auth0.com/t/force-a-specific-enterprise-connection-id-for-new-universal-login/100567/2 "2023-02-16T14:16:51Z")

</div>

We found that you can include the connection parameter as an argument at the /authorize endpoint. This serves our purpose.

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [February 17, 2023, 6:03pm UTC](https://community.auth0.com/t/force-a-specific-enterprise-connection-id-for-new-universal-login/100567/4 "2023-02-17T18:03:29Z")

</div>

Hi @matt.scachette,

That’s correct! You can pass the optional `connection` parameter with your preferred connection in the `/authorize` request to force users to sign in with that specific connection. [Reference: [Add Login Using the Authorization Code Flow](https://auth0.com/docs/get-started/authentication-and-authorization-flow/add-login-auth-code-flow#:~:text=connection,of%20your%20application.)]

Please reach out if you have any additional questions.

Thanks,  
Rueben

---

<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:** [March 3, 2023, 6:03pm UTC](https://community.auth0.com/t/force-a-specific-enterprise-connection-id-for-new-universal-login/100567/5 "2023-03-03T18:03:47Z")

</div>

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