Serge Huber created UNOMI-1039:
----------------------------------
Summary: Tracker: test deployments where the website and Unomi are
on different domains
Key: UNOMI-1039
URL: https://issues.apache.org/jira/browse/UNOMI-1039
Project: Apache Unomi
Issue Type: Sub-task
Components: unomi-tracker
Reporter: Serge Huber
Fix For: unomi-tracker-2.1.0
Many websites call a Unomi server on another domain. Browsers then treat the
Unomi profile cookie as a third-party cookie, and Safari blocks it, so visitors
are not recognised. The tests do not cover this today: the test page and Unomi
are all on localhost, which browsers treat as one site.
Tests to add, recording how the tracker behaves today in each case (profile
kept across page loads and across sessions, events stored):
* Unomi behind a reverse proxy on the website's host (a /unomi path in the test
server), with a contextServerUrl that has a path.
* Unomi on another host of the same domain, and on another domain, using host
names mapped to localhost in Chromium (--host-resolver-rules) and HTTPS with a
test certificate (needed for SameSite=None cookies).
* Third-party cookies blocked in Chromium (what Safari does), and the same
tests in Playwright's WebKit and Firefox.
When UNOMI-733 lets the tracker keep the profile itself, the blocked-cookie
cases change from "new profile" to "same profile".
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
