Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

If yes, is there a way to prevent this? Have the payload be validated by the identity schema and either silently ignore fields not on the schema or even throw an error?

That's just how JSONSchema works: <https://json-schema.org/understanding-json-schema/reference/object.html#additional-properties>

I read the linked resource. Does that mean I can prevent additional properties somehow by specifying this?
```"additionalProperties": false```

Is this a valid approach? Or would that be considered a misuse of the identity schema?

I was honestly surprised that the client can store any arbitrary key/value pair in the traits of his/her profile.