W
W
weslyg2019-07-26 20:34:02
API
weslyg, 2019-07-26 20:34:02

Where to store users?

Suppose I have some kind of API in which there is some kind of logic and it all works fine, but I understand that I need users and roles, of course, I can go and create a plate with both of them and implement it, but I have a question, do I really have to do this? Implement registration, password change, make sure that it is safe, convenient, and productive? Why, when I need to store conditional JAR packages, I am able to install a store for myself and just configure it, and with users, all the guides that I see come down to describing the OpenID / Oauth2 protocols. It’s not very clear to me, is there really no good open source implementation of all actions related to users?
Googling, I came across the concept of identity & access management (IAM) and as I understand it, such systems just allow you to implement something similar. The most adequate are Gluu, CAS, Keycloak. But looking at them, you understand that this is also a kind of harvester of everyone. There you have Web admin, and immediately screwed OpenId for your clients, and integration with AD. But it’s not clear to me whether I really need such a large tool, and I still don’t understand where it will eventually store users, and whether I need to implement registration and password change methods.
Are there any ready-made solutions in this regard, or will only a sign with users in my apishka save me?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
I
Ivan Shumov, 2019-07-26
@inoise

Well, if there are not a lot of users or there is money - Auth0 will help. And so - Keycloak top

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question