Keycloak – Open-Source Identity and Access Management Interview

Re:Keycloak – Open-Source Identity and Access Management Int... by mmgutz on Monday June 19, 2023 @03:40AM (#36388357)

The big auth companies have been really good at creating those "Don't roll your own auth EVER!!!" articles.

You're not alone. I take it a step further and don't deal with passwords. I use login through email, in which I send a nonce to the user's email. The users enter that nonce to log in. This is what many online bank apps do. That reduces the security surface area to CSRF, securing cookies and session expiry. Most popular frameworks should handle that part of it.

[ Parent | on HN ]

Re:Keycloak – Open-Source Identity and Access Management Int... by benoliver999 on Monday June 19, 2023 @03:59AM (#36388469)

I like this solution and use it on a system where MFA is not an option, and people log into it very infrequently.

Initially people told me to use a login link or 'magic link'. However it quickly became clear that they also wanted to receive the code on a different device to the one they logged in with.

[ Parent | on HN ]

Re:Keycloak – Open-Source Identity and Access Management Int... by SahAssar on Monday June 19, 2023 @05:29AM (#36389043)

> That reduces the security surface area to CSRF, securing cookies and session expiry

How do you keep the user logged in? Do you just keep a token in-memory on your frontend app?

[ Parent | on HN ]