[ 
https://issues.apache.org/jira/browse/UNOMI-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18138033#comment-18138033
 ] 

Serge Huber commented on UNOMI-1019:
------------------------------------

Done for unomi-tracker 2.0.0: tenant public API key (#27), build on install 
from git (#31), deployment docs (#38), release docs (#40), all in 
https://github.com/apache/unomi-tracker.

> Make unomi-tracker compatible with both V2/V3 and V4
> ----------------------------------------------------
>
>                 Key: UNOMI-1019
>                 URL: https://issues.apache.org/jira/browse/UNOMI-1019
>             Project: Apache Unomi
>          Issue Type: Improvement
>          Components: unomi-tracker
>    Affects Versions: unomi-tracker-1.5.0
>            Reporter: Serge Huber
>            Assignee: Serge Huber
>            Priority: Major
>             Fix For: unomi-4.0.0, unomi-tracker-2.0.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> h3. Summary
> Unomi 4 can host several separate customers (tenants) on one server, but the 
> web tracker cannot say which customer a website belongs to, so it cannot be 
> used with a multi-tenant Unomi 4 server. The goal is one tracker for all 
> Unomi versions, chosen by configuration.
> Technical detail: Unomi 4 needs the tenant public API key in the 
> X-Unomi-Api-Key header on context.json and eventcollector, unless 
> compatibility mode is on.
> h3. Approach
> * New optional wemInitConfig.apiKey, sent as X-Unomi-Api-Key; without it, 
> requests are unchanged. Public key only, as visitors can see it.
> * No tenant ID setting: the public key identifies the tenant.
> * Older servers ignore the header. It adds a CORS preflight per request.
> * Released as tracker 2.0.0, a drop-in for 1.x; 1.x stays for Unomi 2.x and 
> 3.x, fixes only.
> h3. Changes
> * Tracker: https://github.com/apache/unomi-tracker/pull/27
> * Manual: https://github.com/apache/unomi/pull/925
> * Follow-up: update the tracker bundled in Unomi from 1.4.0 to 2.0.0.
> h3. How to test
> * Unit tests for the header, set and not set.
> * yarn test:servers against Unomi 2.x, 3.x and 4.x.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to