4 ms·
Congrats on the launch! I'm curious about how this compares to existing Auth microservice solutions like Ory Kratos[0][1]. For the "short-lived tokens" that you
by freeqaz 5y ago
Congrats on the launch! I'm curious about how this compares to existing Auth microservice solutions like Ory Kratos[0][1]. For the "short-lived tokens" that you mention, is that similar to Ory Kratos used with Ory Oathkeeper[2][3] with JWTs? That's a similar approach that I've seen companies like Uber taking for their microservice Auth.
0: https://www.ory.sh/kratos/ https://www.ory.sh/kratos/
1: https://github.com/ory/kratos https://github.com/ory/kratos
2: https://www.ory.sh/docs/kratos/guides/zero-trust-iap-proxy-identity-access-proxy https://www.ory.sh/docs/kratos/guides/zero-trust-iap-proxy-i...
3: https://github.com/ory/oathkeeper https://github.com/ory/oathkeeper
- sebmellen 5y agoI could imagine that this is just a wrapper around ORY services.
- aisrael 5y agoYup, the short lived tokens are JWTs - wasn't sure how much detail to go into in the description. For comparing to something like Kratos, probably the best way of putting it is, the first line of the quickstart guide for Kratos is "Ory Kratos has several moving parts and getting everything right from the beginning can be challenging" - and we want to provide the opposite initial experience. We want there to be an understandable UI for login + team management that you can interact with immediately and quickly configure. Kratos and Oathkeeper are really cool though, especially when you want to go significantly deeper in tuning things. As we add on more complexity, we want to make sure that that initial experience is still really walk up usable.
- jeswin 5y ago> Ory Kratos has several moving parts and getting everything right from the beginning can be challenging That's them overstating it. You could deploy it in couple of hours (in its simplest form).