handsome-agency-20541
01/09/2023, 4:41 PMhandsome-agency-20541
01/10/2023, 11:57 AMmagnificent-energy-493
handsome-agency-20541
01/10/2023, 12:23 PMHow do you determine if a users password gets leaked?I, as a developer, am not the very best person to answer this question. I guess our InfoSec department would come up with a dozen of crazy scenarios. 🙈 In our case we’re talking of corporate accounts, so a leak is not necessarily public.
Then you could for example delete the password credential that has been leaked
https://www.ory.sh/docs/reference/api#tag/identity/operation/updateIdentityTried that yesterday, but looks like either I’m doing something wrong, or credentials can’t be deleted
curl -q -H 'Authorization: Bearer '$ORY_PAT $ORY_HTTP_BASE'/admin/identities/a16986bf-dfd0-42a4-a589-b1573dea5dcc' -XPATCH -H 'Content-type: application/json' -d '[{"op":"remove", "path": "/credentials/password"}]' | jq
handsome-agency-20541
01/10/2023, 12:25 PM[{"op":"remove", "path": "/credentials"}]
, got patch includes denied path: /credentials
.magnificent-energy-493
magnificent-energy-493
curl -d "@identity.json" -X PUT <https://asd.projects.oryapis.com/admin/identities/1234> \
--header 'Authorization: Bearer ory_pat_asd \
--header 'Content-Type: application/json'
### Create login flow for browser
handsome-agency-20541
01/10/2023, 2:56 PM.credentials.password
• without .credentials
• with .credentials.password
set to null
Kratos did not reset the password.
Managed to replace the password with a new cleartext one. E.g. jq '.credentials.password.config = { password: "random" }'
. Okay, that could work.