Ask HN: What are problems with implementing authentication and authorization?
Hey y'all,
I would like to hear strange problems you encountered while working on authentication and authorization (when you work on a mobile app, or web app, etc...)? What are things you did not think of before implementing your system. How would you avoid such problems?
If you are using Identity and User Management Services (or probably you work there) like Auth0 (or others), why are you using it and what are you missing?
(
5 comments
| 8 points
| on HN
)
Problems I encountered:
* Normalized user profile using data from various identity providers [1].
* Passwordless login [2].
* Using custom SMS gateway for passwordless login or 2FA [3]
There are not a stable, polished, feature rich alternatives to Auth0 that are affordable. I know that's a lot to ask for, but since you're asking. Auth0 is very nice, but prohibitively expensive. There are also not a lot of maintained and stable alternatives. Pretty much the only one I am aware of is Keycloak.
[1] https://auth0.com/docs/users/normalized/auth0
[2] https://auth0.com/passwordless
[3] https://auth0.com/docs/connections/passwordless/guides/use-s...
Yeah, the problem with having 100 different user information and not one standardized way, is a big problem, do you think Auth0 and Keycloak(if they normalize) solve this problem in the best possible way?
Passwordless logins and 2FA are a good thing to point out. I will take a closer look at these "problems"/"solutions".
Also on the note of cookies, modern browser do not delete session or stale cookies if the browser was not closed properly, eg. the user just shutdown the system without closing the browser.
Jeah, domain wise if you have a cookie set for example.com and test.example.com, if the user is on the later it would send both cookies. This may be wanted for a common login system. In general yes it can be avoided if potential conflicting apps use different cookie names by default.