Open nsklikas opened 6 months ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/IAM-868.
This message was autogenerated
Issue has been introduced by https://github.com/ory/kratos/commit/e3bfa109908e492f62353a275281d95dc5226196
the change in the hydra-client-go/v2
library version from a side branch introduces a json decoder and calls the DisallowUnknownFields
which breaks everything on our side
issue reported upstream https://github.com/ory/kratos/issues/3904
With the addition of token lifespans to the client configuration, hydra 2.3.0(fork) does not work with with kratos 1.1.0. The reason is that when Kratos tries to fetch the hydra login flow using the login_challenge, the flow that hydra returns includes the client. The client metadata contain the new lifespan fields and kratos throws an error because it does not allow extra fields when parsing the hydra responses. This issue does not occur with kratos v1.0.0
To overcome this we could remove the hydra configuration from kratos and handle the flow from the login UI.
To reproduce this you can:
.env
, rundocker compose up --build --remove-orphans