[PUBTSKCONF-6] DOC: warn about potential path conflicts Created: 26/Jul/23  Updated: 28/Jul/23  Resolved: 28/Jul/23

Status: Closed
Project: Publication Task Configuration
Component/s: None
Affects Version/s: 6.1.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Viet Nguyen Assignee: Richard Gange
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 20m
Original Estimate: Not Specified

Issue Links:
causality
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Reproduce

  1.  Create let's say 2 websites having 2 root pages like this example "/mygroup" and "/mygroupvn" pages
  2.  Then configure group mapping as described from our docs here. Note that let's say group "ga" map to "/mygroup" and "vn" map to "/mygroupvn" for example.

Expected
System send notifications to the right users in group

Actual
Once publisher in "vn" group publish content, it send notification to users in "ga" group.

Workaround
Reorder the group mappings so the more specific path is checked first.

Notes

  • Issue may caused by below matching which uses "startsWith" operation in our GroupMappingAwareParameterResolver::getGroups (code here)
  • However "startsWith" is needed to catch all subpaths of the configured path. We cannot simply switch to "equals" because then all subpaths would fall into the default case.


 Comments   
Comment by Richard Gange [ 26/Jul/23 ]

For now I think we'll mention this corner case in the warnings section of the docs.

Generated at Mon Feb 12 10:32:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.