If this is not a spin on the linked article, that would definitely be terrifying. A bit as if stack overflow and reddit had a baby.
If it is a spin, the identity system used is a popular open source system which you can find at https://github.com/ory/kratos. The react code is a reference implementation of the same people who wrote that thing, and the article is intended to help people get started with the open source stack. So if you were indeed applying for a job interview, and the task would be to write such an app - you would know where to look. Plus, this would probably reduce the amount of terrible login solutions we have today in the WWW ;)
ORY Kratos is new to me. I've noticed it's only at v0.5, but I don't quite understand what that means since the Read Me's stats suggest it's production-ready. If that's true, the version number seems like a disconnect. (Or am I the only one for whom pre-1.0 version numbers suggest "for development only"?)
I still can’t wrap my head around Kratos even though I’ve wanted to deploy it since it conceptually sounds great.
So do I build my own login screens? If not, do they come out of the box? If so then is it really api only? Where does it fit in with a single page app architecture?
Is there an example of where a real website has used it and I can see how they implemented it? All I see is either too conceptual in the screen cast, or haven’t seen any real websites.
Do I still have to build all the emails for forgot password etc.
They have that info on github [0]. Basically it handles all of the logic for creating and using accounts with modern best practices, including 2fa and OAuth
In my experience, that probably means they won't deal with all the bullshit one has to go through in setting up inside the firewall in any organisation of sufficient size.
13 comments
[ 3.3 ms ] story [ 49.4 ms ] threadIf every candidate posted their react login code HN would have nothing else!
If it is a spin, the identity system used is a popular open source system which you can find at https://github.com/ory/kratos. The react code is a reference implementation of the same people who wrote that thing, and the article is intended to help people get started with the open source stack. So if you were indeed applying for a job interview, and the task would be to write such an app - you would know where to look. Plus, this would probably reduce the amount of terrible login solutions we have today in the WWW ;)
Hope this helps!
So do I build my own login screens? If not, do they come out of the box? If so then is it really api only? Where does it fit in with a single page app architecture?
Is there an example of where a real website has used it and I can see how they implemented it? All I see is either too conceptual in the screen cast, or haven’t seen any real websites.
Do I still have to build all the emails for forgot password etc.
[0] https://github.com/ory/kratos
It looks like it claims to be "cloud native", but what does that actually mean?
Tongue in cheek, but also not.
"ORY Kratos is the first and only cloud native Identity and User Management System in the world."
Uhhh That's not true... Every major cloud provider has one too, and some have had them for over 5+ years.
Also, do Auth0, Okta, etc count?