Programming

17446 readers

172 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

snowe

Ategon

[email protected]

[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? (lemm.ee)

submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/programming

3 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 12 points 7 months ago (2 children)

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.

[–] [email protected] 5 points 7 months ago

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.

[–] [email protected] 2 points 7 months ago

Ah! That makes sense. Thanks