administrative purposes. All public accesses should always use the /cxs/context.json endpoint for consistency and security. 3.1.4. HOW TO UPDATE A PROFILE FROM THE PUBLIC INTERNET Before we get into coming from the public internet, we’ll quickly talk first about how NOT to do it, because we often see users using the following anti-patterns. HOW NOT TO UPDATE A PROFILE FROM THE PUBLIC INTERNET ubu Unomi. A login event is considered a "privileged" event and therefore for not be initiated from the public internet. Ideally user authentication should always be validated by a trusted third- party even if

. . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.2.3. How to update a profile from the public internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.2.4. How . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 8.20. Important changes in public servlets since version 1.5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 to administrative purposes. All public accesses should always use the /context.json endpoint for consistency and security. 2.2.3. HOW TO UPDATE A PROFILE FROM THE PUBLIC INTERNET Before we get into how

actions that can be accomplished by site (or more precisely scope) visitors. These are tracked in general because they relate to specific business objectives or are relevant to measure site/scope performance it, performs its work and returns an integer status corresponding to what happened as defined by public constants of the EventService interface of Unomi: NO_CHANGE, SESSION_UPDATED or PROFILE_UPDATED