ancient-coat-5565
08/31/2023, 9:50 AM/settings?flow=3e...
The following submit on the settings page triggers a POST call to /self-service/settings?flow=3e...
which leads to a 200 OK
What is concerning, Kratos then removes the state_changed_at
field from the identity, which causes trouble regarding the authentication afterwards. Basically the identity authentication is broken after that.
Q: is it intended that the state_changed_at
property gets dropped by Kratos? If yes, why?
Q2: what process drops this property?
ty!ancient-coat-5565
08/31/2023, 12:51 PMupdated_at
field on the identity does not get updated. Is this a bug? šancient-coat-5565
08/31/2023, 1:28 PMancient-coat-5565
08/31/2023, 1:29 PMnull
Looked into the traces and the following update query is run:
UPDATE "identities" AS identities SET "created_at" = $1, "metadata_admin" = $2, "metadata_public" = $3, "nid" = $4, "schema_id" = $5, "state" = $6, "state_changed_at" = $7, "traits" = $8, "updated_at" = $9 WHERE identities.id = $10 AND identities.nid = $11
Probably the arguments there are wrong / invalid.ancient-coat-5565
08/31/2023, 1:30 PMincalculable-shoe-63378
08/31/2023, 5:08 PMancient-coat-5565
08/31/2023, 6:57 PMancient-coat-5565
09/07/2023, 7:14 AMancient-coat-5565
09/07/2023, 7:14 AMmysterious-balloon-83741
11/02/2023, 7:46 AM/self-service/settings
will unset the state_changed_at
Is there any update or fix on this? šmagnificent-energy-493
ancient-coat-5565
11/02/2023, 6:52 PM