Feature/rm 3369 test set clearance
RM-3369 Fix several existing security clearance UI tests.
Use the in-line "Set Clearance" action on the security clearance page and expect the new dialog to
pop up (rather than the dropdown menu that used to be there).
Remove a check on the ordering of the classification levels in the security marks dialog, because
there is now a new issue (RM-3416) to cover this.
Note that this does not cover all acceptance criteria for RM-3010 because the "on-hover"
functionality has not yet been implemented.
See merge request !180
Xperimental/rm 2812 public api test
A unit test to look for compatibility issues within the classes marked public API. The test will fail if it finds any exposed references to Alfresco non-public API classes from those marked as @AlfrescoPublicApi. The test searches within method signatures, fields, constructors, superclasses, inner classes and interfaces of public API classes.
See merge request !158
Feature/rm 3344 admin and guest
RM-3344 Ensure that admin can't lose clearance and guest can't gain any clearance.
Rather than use the guest role, as was used previously for classification clearance, we are
explicitly checking the username.
See merge request !160
This is a first pass at preventing changes to the clearance of admin or guest.
Previously we weren't allowing any changes to their clearance, but when
working with security markings, admin in particular needs to occasionally gain
a new mark when a custom group is created. Currently that clearing is not
happening, but this change does not prevent it, if needed.
Also remove an unused method from the CaveatMarkingServiceImpl, as the class
is already very full.
Xperimental/rm 2812 Mark Public APIs
First attempt to mark classes that should be part of the public API with \@AlfrescoPublicAPI.
I have also added a couple of \@deprecated annotations to classes where I thought it made sense, and
added comments to classes that I wanted to add to the public API but couldn't (due to their contract
being dependent on non-public API classes).
See merge request !138
Feature/rm 3144 patch for clearance level
Create a patch to migrate all users' clearance levels from the old classification model to
the new security marks model.
This merge request depends on getting !130 merged first.
See merge request !133
