# Is Auth0 the right solution for our project?

**URL:** <https://community.auth0.com/t/is-auth0-the-right-solution-for-our-project/106001>\
**Category:** Get Help\
**Tags:** application, sso\
**Created:** [May 2, 2023, 5:14pm UTC](https://community.auth0.com/t/is-auth0-the-right-solution-for-our-project/106001 "2023-05-02T17:14:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![elliot](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/elliot/32/46839_2.png) [@elliot](https://community.auth0.com/u/elliot)\
**Post date:** [May 2, 2023, 5:14pm UTC](https://community.auth0.com/t/is-auth0-the-right-solution-for-our-project/106001/1 "2023-05-02T17:14:14Z")

</div>

Hey everyone,

I’m evaluating Auth0 to add SSO to an existing Meteor (node.js) app. We currently manage our users (auth, roles, profiles, etc) through a traditional username/password database and can rely on built-in authentication packages for permission checking, etc on the front and back-end. Additionally, our app is multi-tenancy running on a single instance with subdomains acting as identifiers for clients. Each subdomain / client will have its own preferences for allowed SSO providers (e.g. google and facebook or just google).

To summarize, our core requirements are:

- Ability for users to login via Auth0 SSO and have them be authenticated through our existing user database (which will allow us to use our existing auth/permission checks)
- Ability for clients to dynamically chose which SSO options are available to their users during login
- Ability to work with custom subdomains / multi-tenancy on a single server instance (wildcard redirect urls might be what I need?)

Thanks so much for the help and I’m happy to answer any follow up questions.

---

<div class="post-metadata">

**Author:** ![elliot](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/elliot/32/46839_2.png) [@elliot](https://community.auth0.com/u/elliot)\
**Post date:** [May 9, 2023, 5:15pm UTC](https://community.auth0.com/t/is-auth0-the-right-solution-for-our-project/106001/3 "2023-05-09T17:15:30Z")

</div>

Bump? Anyone have suggestions here?

---

<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:** [May 25, 2023, 3:21pm UTC](https://community.auth0.com/t/is-auth0-the-right-solution-for-our-project/106001/6 "2023-05-25T15:21:55Z")

</div>

Hi @elliot

Welcome to the Auth0 Community!

We appreciate your effort in evaluating Auth0 for your existing application in terms of answers to your concerns.

1. Auth0 is capable of connecting to an existing external database. After connection, you can choose between using your existing checks or importing them to Auth0 via Actions. [External Databases](https://auth0.com/docs/authenticate/database-connections/custom-db/overview-custom-db-connections), [Actions in External Databases](https://auth0.com/docs/authenticate/database-connections/custom-db#:~:text=the%20IdAM%20pipeline%3A-,Actions,-extend%20processes%20called)
2. Auth0 offers you the possibility to force a login with a specific Social Connection with `connection={connection name) for example, google-oath2`

```auto
GET https://{yourDomain}/authorize?
  audience=API_IDENTIFIER&
  scope=SCOPE&
  response_type=code&
  client_id={yourClientId}&
  redirect_uri={https://yourApp/callback}&
  state=STATE
  connection=google-oauth2

```

1. Auth0 supports wildcards for:

- **Allowed Callback URLs** : List of URLs to which Auth0 is allowed to redirect users after they authenticate.
- **Allowed Logout URLs** : List of URLs to which you can redirect users after they log out from Auth0.
- **Allows Web Origins** : List of URLs from where an authorization request using [Cross-Origin Authentication](https://auth0.com/docs/authenticate/login/cross-origin-authentication), [Device Flow](https://auth0.com/docs/get-started/authentication-and-authorization-flow/device-authorization-flow), and [web\_message as the response mode](https://auth0.com/docs/authenticate/protocols/oauth) can originate.
- **Allowed Origins (CORS)**: List of URLs that will be allowed to make requests from JavaScript to Auth0 API (typically used with CORS).

You can read more details about Subdomain URL Placeholders [here](https://auth0.com/docs/get-started/applications/wildcards-for-subdomains)

---

<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:** [June 8, 2023, 3:22pm UTC](https://community.auth0.com/t/is-auth0-the-right-solution-for-our-project/106001/7 "2023-06-08T15:22:35Z")

</div>

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