To update an identity schema for a specific identity to include the "code" method for passwordless login via email, you need to follow these steps: 1. First, ensure you've updated your identity schema as you've shown:

json "code": {   "identifier": true,   "via": "email" }

This change should be part of the

<http://ory.sh/kratos|ory.sh/kratos>

section under the

credentials

object for the email field in your identity schema. 2. After updating the schema, you need to update the existing identities to use the new schema. This process involves patching the identity with the new schema ID and any necessary trait changes. Here's how you can do it: a. Get the new schema ID (you should have this after creating or updating the schema). b. Use the Ory API to patch the identity. Here's an example using cURL:

bash    curl --location --request PATCH "https://$<http://ORY_SLUG.projects.oryapis.com/admin/identities/$IDENTITY_ID|ORY_SLUG.projects.oryapis.com/admin/identities/$IDENTITY_ID>" \    --header "Authorization: Bearer $ORY_API_KEY" \    --header "Content-Type: application/json" \    --data-raw '[    {        "op": "replace",        "path": "/schema_id",        "value": "{new-schema-id}"    }    ]'

Replace

$ORY_SLUG

,

$IDENTITY_ID

,

$ORY_API_KEY

, and

{new-schema-id}

with your actual values. 3. Verify that the update was successful by retrieving the identity and checking its schema ID and traits. Remember, updating the schema and patching identities should be done carefully, especially in a production environment. It's recommended to test this process thoroughly in a staging environment first. For more detailed information on updating identities to use a new schema, you can refer to the [Ory documentation on updating identities](https://www.ory.sh/docs/identities/model/manage-identity-schema#update-identities-to-use-a-new-schema).

@chilly-king-10285 the schema id for all identities is "default", so should I patch with the id set to default?

Based on the information you've provided, if the schema ID for all identities is "default", you don't need to patch the schema ID itself. The "default" schema ID is typically used when you're updating the content of the default schema, rather than switching to a new schema. In this case, since you've updated the default schema to include the "code" method for passwordless login via email, you need to ensure that the existing identities are compatible with the new schema structure. Here's what you should do: 1. First, verify that your updated schema has been applied correctly. You can do this by checking the current schema using the Ory API. 2. If you're sure the default schema has been updated correctly, you don't need to change the schema_id of the identities. Instead, you might need to update the traits of the identities to ensure they comply with the new schema structure. 3. If there are any new required fields in your updated schema, you'll need to add those to existing identities. In your case, it seems you've only added an optional authentication method, so this step might not be necessary. 4. To be safe, you can still use the PATCH method to ensure the identity is up to date with the new schema structure. Here's an example:

bash curl --location --request PATCH "https://$<http://ORY_SLUG.projects.oryapis.com/admin/identities/$IDENTITY_ID|ORY_SLUG.projects.oryapis.com/admin/identities/$IDENTITY_ID>" \ --header "Authorization: Bearer $ORY_API_KEY" \ --header "Content-Type: application/json" \ --data-raw '[ {     "op": "replace",     "path": "/schema_id",     "value": "default" } ]'

This operation will essentially "refresh" the identity against the current default schema, ensuring it's up to date. 5. After updating, verify that the identity has the correct structure by retrieving it and checking its details. Remember, when working with identity data, it's crucial to be cautious and test thoroughly in a non-production environment first. If you're unsure about any steps, it's always best to consult the [Ory documentation on managing identities](https://www.ory.sh/docs/kratos/manage-identities/overview) or reach out to Ory support for guidance.