You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to PATCH the verifiable_addressesverified and/or status flag is not possible if the identity was created with an uppercase letter in the email.
Reproducing the bug
Use an identity schema with a trait having an email and verification via email enabled.
Create a new identity with an email containing a uppercase letter e.g. Test@test.com
Try to change the verified status of the newly created identity via PATCH using the admin api of kratos: e.g. kratos running locally with exposed admin port 4434 curl -v -X PATCH --data '@./patch.json' -H 'Content-Type: application/json' http://localhost:4434/admin/identities/<the-identity-id>'
where patch.json does contain the patch operation:
Observe the verifiable_addresses was really not updated by issuing a GET request: curl -v -X GET http://localhost:4434/admin/identities/<the-identity-id>'
Repeat the above steps with an email address containing only lowercase letters and the PATCH can be executed
### Version
0.11.1
### On which operating system are you observing this issue?
Linux
### In which environment are you deploying?
Docker
### Additional Context
_No response_
The text was updated successfully, but these errors were encountered:
Preflight checklist
Describe the bug
Trying to PATCH the
verifiable_addresses
verified
and/orstatus
flag is not possible if the identity was created with an uppercase letter in the email.Reproducing the bug
Test@test.com
curl -v -X PATCH --data '@./patch.json' -H 'Content-Type: application/json' http://localhost:4434/admin/identities/<the-identity-id>'
where
patch.json
does contain the patch operation:verifiable_addresses
was not updated and does contain a null-id and null-created-at date:verifiable_addresses
was really not updated by issuing a GET request:curl -v -X GET http://localhost:4434/admin/identities/<the-identity-id>'
Relevant log output
No response
Relevant configuration
The text was updated successfully, but these errors were encountered: