Based on the information provided in the knowledge sources, Ory Kratos allows you to define custom identity schemas and set specific fields as identifiers. However, it's important to note that each identifier must be universally unique. If you try to create or update an identity with an identifier that already exists, the system will reject the request with a 409 Conflict state. This is likely the reason you're seeing the conflict error when trying to create a user with an email already registered with Google SSO. In your case, you want to treat

user_info

as a unique identifier. However, your current schema seems to be setting both

user_info

and

email

as identifiers. If you want to treat

user_info

as the unique identifier and not the email, you should remove the

identifier: true

line from the

email

field in your schema. Here's an example of how you might modify your schema:

json
{
  "$id": "test-identity",
  "title": "Person",
  "type": "object",
  "properties": {
    "traits": {
      "type": "object",
      "properties": {
        "user_info": {
          "type": "object",
          "title": "User Information",
          "properties": {
            "username": {
              "type": "string",
              "title": "Username",
              "maxLength": 100
            },
            "customer_id": {
              "type": "number",
              "title": "Customer Id"
            }
          },
          "<http://ory.sh/kratos|ory.sh/kratos>": {
            "credentials": {
              "password": {
                "identifier": true
              },
              "webauthn": {
                "identifier": true
              },
              "totp": {
                "account_name": true
              }
            }
          }
        },
        "email": {
          "type": "string",
          "format": "email",
          "title": "E-Mail",
          "<http://ory.sh/kratos|ory.sh/kratos>": {
            "recovery": {
              "via": "email"
            },
            "verification": {
              "via": "email"
            }
          },
          "maxLength": 320
        }
      },
      "required": [
        "user_info",
        "email"
      ],
      "additionalProperties": false
    }
  },
  "$schema": "<http://json-schema.org/draft-07/schema#>"
}

Please note that this change will make the

email

field no longer serve as an identifier for password-based authentication. It will still be used for recovery and verification purposes. Also, keep in mind that the

user_info

object as a whole is being treated as the identifier in this schema, not the individual

username

and

customer_id

fields. If you want each of these fields to be unique identifiers, you would need to set

identifier: true

for each of them individually. Finally, remember that changing the identity schema can have significant implications for your application, so it's important to thoroughly test these changes before deploying them to a production environment.

New message text here

New message text here