Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

So, comparing `hydra-login-consent-node` and `kratos-selfservice-ui-node` side by side in the developer tools of the browser, the summary is that when i use the former the /consent call will `POST` to <http://127.0.0.1:3000/consent> resulting in a 302 redirect back to <http://127.0.0.1:4444> while the equivalent `POST` to <http://127.0.0.1:4455/consent> results in a `500`. In this case only the consent URL is different, the login is handled by the kratos UI in both instances… It clearly is the kratos ui code that does not like the /consent POST for some reason while hydra-login-consent accepts it