[Question] Why does Auth0 allow for direct usage of social logins, but with Keycloak I have to register my app at each Identity Provider first?
from abbadon420@lemm.ee to programming@programming.dev on 18 Apr 19:28
https://lemm.ee/post/29785400

So I’m making a project in SpringBoot with Oauth security.

If I use Auth0 as my Authorization Server, I can register an application there and just say that I want user to be able to login with Google an Facebook. That’s all it takes.

If I use Keycloak as my Authorization Server, I can also have users choose Google or Facebook as there prefered login, but in order to provide that, I have to register my app with Google and Facebook first.

So how come it’s so easy with Auth0 and a little less easy with Keycloak? Is it a contract thing, does Auth0 have contracts with all these providers or something?

#programming

threaded - newest

[deleted] on 18 Apr 20:59 next collapse

.

carleeno@reddthat.com on 18 Apr 21:58 collapse

It’s because you’re using the dev environment which uses Auth0’s own keys. You’ll still have to jump through all of those same hoops when you set up a staging or prod environment.

lemmyvore@feddit.nl on 19 Apr 00:26 next collapse

Seconded. There’s no way to do OAuth with Google or Facebook without registering your app with them. The only reason it works with Auth0 is because they’re supplying the app for you, but only during development.

abbadon420@lemm.ee on 19 Apr 06:03 collapse

Ah! That makes sense. Thanks