[OAK-6318] Refactor oak.spi.security into a separate module/bundle

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.10, 1.8.0
• Component/s: core, security
• Epic Link: Modularisation of Oak
• Assignee: Angela Schreiber
• Reporter: Angela Schreiber
• Created: 08/Jun/17 09:38
• Updated: 08/Jan/18 13:36
• Resolved: 12/Oct/17 10:46

Description

In the light of the modularization effort it would IMHO make a lot of sense to refactor oak.spi.security.* into a separate module/bundle that could be release independent of oak-core.

As far as I could see so far this is currently not easily doable due to the dependency of oak.spi.security.* on oak.plugins.tree, which in turn relies on o.a.j.oak.query.QueryEngineSettings and other oak-core internals (see also OAK-6304). Most likely this issue would therefore require a complete review (and possibly a split) of the oak.plugins.tree package space which contains a mixture of utilities and 'API' (like e.g. TreeContext and TreeLocation)... will open a separate issue for this linking to this one.

cc: stillalex, rombert, mduerig, tmueller

Issue Links

• is blocked by: OAK-6681 Remove PropInfo dependency on EffectiveNodeType
• is blocked by: OAK-6690 Refactor constants classes NodeTypeConstants, NamespaceConstants, VersionConstants
• is blocked by: OAK-6703 Refactor oak.namepath package
• is blocked by: OAK-6708 Move plugins.value.jcr package to oak-store-spi
• is blocked by: OAK-6319 Review API and Utilities in oak.plugins.tree package
• is blocked by: OAK-6698 Refactor UUID utilites from IdentifierManager to new UUIDUtils in oak-commons
• is duplicated by: OAK-6658 Move oak.spi.xml to oak-security-spi
• is required by: OAK-6821 Enforce minimum line coverage for oak-security-spi

Sub-Tasks

• Replace usage of RootFactory and TreeFactory in spi.security test: Closed
• Replaces usage of NamePathMapper implementations in AbstractAccessControlListTest: Closed
• Create empty module structure and dependencies from/to other oak modules: Closed