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

It seems like the 2.2.0 release of hydra has a breaking change, regarding correlation of login and consent requests.
The docs for `/admin/oauth2/auth/requests/consent` specifies that this field:
```login_challenge	
LoginChallenge is the login challenge this consent challenge belongs to. It can be used to associate a login and consent request in the login &amp; consent app.```
Which is true for 2.1.0
But for 2.2.0, the `login_challenge` field still contains the short (32 character) id, while the actual login requests contains the new, and very long, encoded id.
The short id not shown anywhere else, making it quite hard to correlate the 2 requests.

Is this intended and/or is there a workaround ?