. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 6.1. Setting up access to the privacy endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . testing REST API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 10.2.5. Setting up Streaming Push queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . map the event data to the profile. This is simpler than it sounds, as usually all it requires is setting up a simple rule and you’re ready to update profiles using events. This is also the safest way to

map the event data to the profile. This is simpler than it sounds, as usually all it requires is setting up a simple rule, defining the corresponding JSON schema and you’re ready to update profiles using ElasticSearch server(s). But if you need to trust all certificates automatically, you can use this setting: 4.14.3. PERMISSIONS Apache Unomi requires a particular set of Elasticsearch permissions for its similar to additionalProperties except that it can recognize properties declared in sub schemas. When setting the unevaluatedProperties value to false, the properties which are not present in the properties

CONTENT OF THE RESPONSE The clients can also specify which information to include in the response by setting the requireSegments property to true if segments the current profile matches should be returned triggers and not only once per session by setting raiseEventOnlyOnceForSession to false, which is not strictly required since that is the default. A similar setting (raiseEventOnlyOnceForProfile) can be /plugins/security) Apache Unomi 1.1.x - Documentation - 25 You can adjust this setting by using the following setting in the $MY_KARAF_HOME/etc/elasticsearch.yml file : security.ipranges: localhost