#What Are Your Thoughts On FusionAuth?

20 messages · Page 1 of 1 (latest)

frosty flicker
#

Hello, has anyone here used FusionAuth on a project? I think it would work for what I'm looking for but wanted to see if anyone had thoughts or experience with it. My use case: A way to centralize a user's db and login between three applications.

tough topaz
#

or even open source solutions

frosty flicker
tough topaz
#

the one i linked

#

and keycloak

#

though if you are working with laravel, i'd probably use passport

#

and well, read a lot into oauth before you even beginn

narrow raft
#

So Passport isn't going to do SSO between three apps out of the box, not "simply" anyway
@frosty flicker
It depends - are you intending to provide authentication?
Is there a "Main" app that will provide the registration etc?

OR - do you not care about providing the authentication (i.e. username/password) and are going to rely on external IdPs (e.g. Google/Azure/their MSFT tenant etc) for authentication, and you just care about authorisation

#

It depends on the use case etc

#

I've got apps that have zero "classic authentication", as they're only used by corporates, who bring their own authentication (MSFT Azure/Google/AWS/Shibboleth)

#

Then I've also got mixed, and "classic authentication" apps

#

it's entirely based on your user case, requirements and approach

tough topaz
#

@narrow raft passport is a full oauth server implementation, so you could use it as standalone sso for other services

narrow raft
#

Yeah, that's why I caveated my response with "not simply" 😄

#

It all depends on what johnsmith's context is, you can absolutely setup an IdP with passport

#

There are other options as well, if everything is Laravel, such as syncing users between instances etc, all depends what the ultimate goal is etc

frosty flicker
#

I'm working on centralizing authentication and authorization for three separate applications:

  • An internal app for admins.
  • Two different tenanted applications where a user might be part of one or both.

I know that these could be combined, but they're separate for good reasons—each has a fundamentally different structure, and keeping them distinct makes things cleaner. All of these apps are still in development, so there's some room to adjust things if needed.

Here's what I'm aiming for:

  • User signs up or logs in.
  • Based on their role or which apps they're associated with, they get routed to the right place.

Basically, I'm looking to build something like 'portal.example.com' that handles:

  • User storage
  • Managing which users belong to which apps
  • Login/sign-up
  • 2FA and password resets
  • Routing users to the correct app

It's essentially a gateway for all user management across the apps.

If you need more details or want to dig into any specific part, just let me know.

narrow raft
#

Okay, Passport could definitely help you out here, given that you have a Central App that handles the authentication etc

#

I will say, it's not going to be a couple of clicks and done, there is a bit more to it