Show HN: Open-source OAuth2 & OpenID server Ory Hydra v2 | Hacker News Reader

Show HN: Open-source OAuth2 & OpenID server Ory Hydra v2

github.com

108 pointsbaconfly14 comments

Hey there :) Co-maintainer here and available to answer all your questions.

Bringing this to v2 was a big one year effort with lots of community contributions and we are excited to finally be able to show it to the world!

Does Hydra integrate with nginx or envoy external authorization? If so, is there a good example you could share?

I’ve relied on oauth2proxy with Dex as an oidc issuer for this purpose for years. This works but I’m trying to understand if Ory is an advancement in functionality.

Absolutely, Ory Hydra supports basic OAuth2 standards like OAuth2 Introspection - if the technology supports these standards then it is compatible!

Is this library the way to go when I have the following needs? 1. Login to SaaS via website and later use an access token to authorize against a graphql api? 2. Login programmatically so an access token can be retrieved and used for REST queries. 3. Does (2) work if the client is a pure oauth2 client (not an oidc client)? 4. Is the library recommended in a tenant based SaaS (like MS Azure)?

Awesome set of release notes, thanks for all the hard work!

Excited to find time to dig into v2 changes, feels like Hydra has corrected a lot of long standing issues and made it much easier to use (I haven't run Kratos yet but having the integration be tighter makes so much sense).

Is there a good description of oathkeeper vs keto? It seems like oathkeeper would use keto but I'm not sure if they're similarly tightly integrated.

Thank you for the kind words :)

Ory Keto and Ory Oathkeeper can play together! Ory Keto implements Google Zanzibar, it's basically a service where you can check if "x is allowed to do y". Ory Oathkeeper on the other hand is something which can check for any given HTTP request: who is the user making the request? is the user allowed to make the request? and finally convert all this information into a common format. However, Ory Oathkeeper does itself not make the decision, it uses e.g. Ory Keto to check the permission itself. Hope this makes sense

This has been a long time in the making, many kudos for all the hard work by the maintainers and contributors! Really excited about the integration with the ory kratos idp, should make building SSO much easier.

Kudos on the release!

I get a 404 when clicking on the SDKs link in the github readme: https://www.ory.sh/docs/hydra/sdk

The correct link is probably https://www.ory.sh/docs/kratos/sdk/index

Thank you, fixed! :)

There is also a node-js library called node-oidc-provider. Does anyone know how those libraries compare?

How does it compare to keycloak?

Hydra is a plain oidc and south implementation.

It doesn't provide a login screen, you need to implement your own flow user interface and use their their api to interface with the auth server.

This is great for the flexibility you have.

Keyckoak covers the basics outh of the box and have a login page implementation ready.

I use Hydra v1 and it is great! Looking forward to test v2!

excited to try this again!

Reply on news.ycombinator.com