Hey everyone 👋 I'm trying to upgrade Hydra to

v2.2.0

and encountering an issue with the

ConsentRequest

now that Hydra is using an AEAD-encoded flow. When getting the

ConsentRequest

from my consent app, the

login_challenge

from the

GetConsentRequest

response doesn't match the

AEAD-encoded

login challenge. In the API documentation for

Get Consent Request

it says:

LoginChallenge is the login challenge this consent challenge belongs to. It can be used to associate a login and consent request in the login & consent app.

This doesn't seem to be the case anymore or do I miss something? 🤔 Any pointers / help would be appreciated. Thanks!

Hello @straight-action-4068 thanks for reaching out! This is a good channel to post this - #C02PSRUGUAV is also an option. I personally don't have experience with this upgrade path - but we do offer professional support agreements for this kind of work as well. This would mean Ory engineers support you directly with the upgrade and also with any other issues you might have in the future. Without a support agreement you will have to rely on community support - which is great but not always able to cover more "exotic" questions. If you are interested in getting a support agreement in place, please contact us here.

Hi @magnificent-energy-493 It's not really about the upgrade itself, but I think we found a bug with the new version. I opened an issue on the ory hydra github repo: https://github.com/ory/hydra/issues/3887 Thanks!

I see. A support agreement would also cover fixing bugs on a committed timeline and can also include feature requests (depending on the feature ofc). We will look at the issue regardless of agreement ofc but can't say when or if we are able to address it.

Hey Vincent, thx a lot!