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

Since i jumped the bandwagon a bit early on the 2.2.0, i ran into an issue with the consent handlinig.
we used to be able to correlate login_challenge and consent challenge, by getting the OAuth2ConsentRequest which contains a LoginChallenge field.
```	// 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.
	LoginChallenge *string `json:"login_challenge,omitempty"````
but in the current docker image of 2.2.0, this field is still the “short” form of login_challenge, while the challenges used during the login requests are the new (very long) AEAD-encoding variant.
Is this intended?
Or is there another way to correlate the two now ?