[MGNLPRIV-41] Consistent data privacy across multiple instances Created: 26/Jun/18 Updated: 30/Jan/23 Resolved: 30/Jan/23 |
|
| Status: | Closed |
| Project: | Privacy |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Data privacy 1 | ||||||||
| Team: | |||||||||
| Description |
|
Implement a solution to keep visitors and their personal data in sync across multiple public instances. User stories:
Acceptance criteria:
|
| Comments |
| Comment by Christoph Meier [ 28/Jun/18 ] |
|
If the synchronizing is "too slow" - the opt-in link (which was sent by email) to grant consent may fail, if the request sent by clicking the email-link goes to "the other public node". |
| Comment by Christoph Meier [ 28/Jun/18 ] |
|
Probably only slightly related to this ticket - but I add it here too- since it was discussed on a related doc page (https://goo.gl/iV5Wxn) Manual editing of visitor data with the visitors app must be done on the public context.
(Side note: "Same problem" we have with PUR module.) |
| Comment by Matt Rajkovic [ 30/Jan/23 ] |
|
Very old issue. Closing. |