[jira] [Updated] (UNOMI-733) Improve the tracker to stop using unomi server cookie

["Serge Huber (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/UNOMI-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Serge Huber updated UNOMI-733:
------------------------------
    Fix Version/s: unomi-3.2.0
                       (was: unomi-2.7.0)

> Improve the tracker to stop using unomi server cookie
> -----------------------------------------------------
>
>                 Key: UNOMI-733
>                 URL: https://issues.apache.org/jira/browse/UNOMI-733
>             Project: Apache Unomi
>          Issue Type: Improvement
>            Reporter: romain.gauthier
>            Priority: Major
>             Fix For: unomi-3.2.0
>
>
> Currently, persistence of the profile id on the client side is managed through a cookie set by Apache Unomi server. The goal of this ticket is to implement a new logic in the tracker that would:
> - stop using the cookie set by the unomi server
> - reads the profile id from unomi server response 
> - add the profile id to the http request body when doing requests to unomi server
> - persist the profile id from the client, still using a cookie. The method to persist the profile id should be generic so that it should be easily possible to switch from cookie to anything else (local storage for instance)
> The domain to set the cookie on should be provided in the "wemInitConfig" object. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)