. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 6.1. Setting up access to the privacy endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . is a JSON- serialized version of the ContextRequest Java class. Note that it is also possible to access a profile’s data through the /cxs/profiles/ endpoint but that really should be reserved to administrative requires 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

org/unomi-api/apidocs/org/apache/unomi/api/ContextRequest.html) Java class. Note that it is also possible to access a profile’s data through the /cxs/profiles/ endpoint but that really should be reserved to administrative requires 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 using Basic or Digest HTTP auth. By default, the login/password for the REST API full administrative access is "karaf/karaf". The generated package is also configured with a default SSL certificate. You can

~/java/deployments/unomi/apache-karaf-3.0.1/deploy/ . If all went smoothly, you should be able to access the context script here : http://localhost:8181/cxs/cluster . You should be able to login with using Unomi plugins or via the provided REST APIs. However, access to REST APIs is restricted due for security reasons, requiring privileged access to the Unomi server, making things a little more complex need to provide any authentication at all to interact with this part of Unomi since we only have access to read-only data (as well as providing events as we shall see later on). If we had been using the