big-evening-36539
09/13/2023, 1:21 PM{
"identity": {
"verifiable_addresses": [
{
"status": "completed",
"value": "<email-here>",
"verified": true,
"via": "email"
}
]
}
}
however, if I do a whoami call I see that the verifiable addresses is not updated. Have I missed something?bland-eye-99092
09/13/2023, 1:23 PMbig-evening-36539
09/13/2023, 1:24 PMbland-eye-99092
09/13/2023, 1:25 PMbig-evening-36539
09/13/2023, 1:25 PMbig-evening-36539
09/13/2023, 1:28 PMbig-evening-36539
09/13/2023, 1:29 PMverifiable_addresses
field; should I also include traits, schema_id, id, ... and other fields?big-evening-36539
09/13/2023, 1:33 PMbland-eye-99092
09/13/2023, 1:33 PMbig-evening-36539
09/13/2023, 1:37 PMcan you try without the webhook entirely?Not sure what you mean here? Only other way to get verified address would be to complete a verification flow? schema:
{
"$id": "<https://schemas.ory.sh/presets/kratos/quickstart/email-password/identity.schema.json>",
"title": "Person",
"type": "object",
"properties": {
"traits": {
"type": "object",
"properties": {
"email": {
"type": "string",
"format": "email",
"title": "E-Mail",
"minLength": 3,
"<http://ory.sh/kratos|ory.sh/kratos>": {
"credentials": {
"password": {
"identifier": true
}
},
"verification": {
"via": "email"
},
"recovery": {
"via": "email"
}
}
},
"name": {
"type": "object",
"properties": {
"first": {
"title": "First Name",
"type": "string",
"minLength": 1
},
"last": {
"title": "Last Name",
"type": "string",
"minLength": 1
}
},
"required": [
"first",
"last"
]
}
},
"required": [
"email"
],
"additionalProperties": false
}
}
}
bland-eye-99092
09/13/2023, 1:42 PMOnly other way to get verified address would be to complete a verification flow?No, it’s built into the recovery flow, to also verify the address See here https://www.ory.sh/docs/kratos/self-service/flows/account-recovery-password-reset#account-recovery-address (At least it should, it might not work for the admin API initiated recovery links.)
big-evening-36539
09/13/2023, 1:45 PM(At least it should, it might not work for the admin API initiated recovery links.)Alright, would be nice to know if it's treated different for admin API initiated recovery links 🙂 My end goal is to make a user be verified and "ready" to use our application by clicking on the recovery link from e-mail and set up password or SSO. So I think I can perhaps verify the user during post settings webhook instead when updating the credentials, and I think I'll achieve what I want(?)
bland-eye-99092
09/13/2023, 1:50 PMbig-evening-36539
09/13/2023, 1:53 PM> hooks:
> - config:
> auth:
> config:
> in: header
> name: Authorization
> value: Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> type: api_key
> body: // link to jsonnet: {user_id: string}
> can_interrupt: false
> method: POST
> response:
> ignore: false
> parse: true
> url: // our verify login endpoint
> hook: web_hook
under recovery.after.hooksbig-evening-36539
09/13/2023, 1:55 PMas we don’t strictly have the confirmation that the user actually received an email on the address, when using the Admin API to generate the code.if you expose the recovery link over email to that user and they click it, wouldn't that confirm that they are the owner of that email?
bland-eye-99092
09/13/2023, 2:01 PMbig-evening-36539
09/13/2023, 2:02 PMbland-eye-99092
09/13/2023, 2:03 PMbig-evening-36539
09/13/2023, 3:42 PMory get identity-config
the value was blank. Had to update via cli to make it work
• Also update webhook via the new frontend looks great, but for us with crappy GPU's the blur makes everything pretty laggy 😛bland-eye-99092
09/13/2023, 3:45 PM