authenticated access. The temptation can be great to use this endpoint because it is simple to access but the risk is that developers might include the credentials to access it in non-secure parts of code such as deactivated by default. If you run into compatibility issues you could reactivate it but it is at your own risk. org.apache.unomi.security.properties.useOGNLScripting=${env:UNOMI_SCRIPTING_USE_OGNL:-false} # This {{url}}/cxs/jsonSchema/delete with the id of the schema into the payload of the request Example: 5.2.5. ERROR MANAGEMENT When calling an endpoint with invalid data, such as an invalid value for the sessionId property

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 5. Consent management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 6. Privacy management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . authenticated access. The temptation can be great to use this endpoint because it is simple to access but the risk is that developers might include the credentials to access it in non- secure parts of code such as

and context server integrators. Context server clients are usually web applications or content management systems. They interact with Unomi by providing raw, uninterpreted contextual data in the form