I stopped comparing the Ory stack to Keycloak some time ago. As you know, I like the modularity of Ory better than the single Keycloak deployment. However, what always gets me when deploying authn is that it releases the cat from the bag. Authz and additional sessions almost always come as a requirement right after.
Last Kratos I looked at was 0.6 so fairly aged by now. Have you had a chance to make the Kratos/Hydra/Keto integration a little bit … less abstract? From memory, integrating Kratos and Hydra reqired a ton of glue code one had to write themselves. That’s the reason why I always reach for Keycloak.
Sorry for the somewhat late answer, but we recently released Hydra 2.0 which makes the Kratos/Hydra integration much easier. You can also get it out of the box on the managed service (+ a ton of other features).
You need a simple consent page for the integration and that is it basically.
Check it out sometime :-)
I stopped comparing the Ory stack to Keycloak some time ago. As you know, I like the modularity of Ory better than the single Keycloak deployment. However, what always gets me when deploying authn is that it releases the cat from the bag. Authz and additional sessions almost always come as a requirement right after.
Last Kratos I looked at was 0.6 so fairly aged by now. Have you had a chance to make the Kratos/Hydra/Keto integration a little bit … less abstract? From memory, integrating Kratos and Hydra reqired a ton of glue code one had to write themselves. That’s the reason why I always reach for Keycloak.