[OAK-1448] Tool to detect and possibly fix permission store inconsistencies

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Later
• Component/s: core
• Labels: production resilience tools
• Assignee: Angela Schreiber
• Reporter: Michael Marth
• Created: 21/Feb/14 12:08
• Updated: 16/Feb/17 08:13
• Resolved: 10/Nov/16 15:44

Description

I think we should prepare for cases where the permission store (managed as a tree mirrored to the content tree) goes out of sync with the content tree for whatever reason.

Ideally, that would be an online tool (maybe exposed via JMX) that goes back the MVCC revisions to find the offending commit (so that have a chance to reduce the number of such occurences) and fixes the inconsistency on head.

Issue Links

• is blocked by: OAK-1706 Add RestrictionProvider#getPattern(String,Set<Restriction>)
• is cloned by: OAK-5685 Tool to detect permission store inconsistencies
• is required by: OAK-2015 PermissionStore doesn't reflect dynamic nature of jcr:all