F*
F+
F*
F*
Domain
Admins
Everyone
F*
F*
F*
F*
SYSTEM
W D
-W -D
W -D
-W -D
Archivists
W -D
W -D
-W -D
W D
Editors
W -D
-F
W D
-W -D
Ingestors
W -D
W D
-W -D
W -D
Producers
L R*
L R*
L R*
L R*
Viewers
K2 Services
•
F
= Full Control
•
L
= List Folder Contents
•
R
= Read
•
W
= Write
•
D
= Delete
•
- = Deny
•
* = Inherits permissions from the folder directly above it
•
** = Inheritance is blocked at this level
Testing
After creating and configuring the Domain Controller and setting permissions for
Aurora Edit bins, you should test the system to make sure that the security is working:
1. Aurora Edit system operation:
Basically, check that permissions exist functionally where they should and that
permissions are denied functionally where they should be denied. A Viewer
user should not be able to write or delete. Significantly, where a user is denied
all permissions (as might be the case for an investigative report that should be
editable by only a small group) make sure that users outside the group have no
access and no availability in the private group. Check that delete permissions
are truly denied. Check that read only users in a particular bin cannot write.
2. Winking:
Winking requires a complicated security relationship between several processes.
Therefore, it’s important to check that users who were expected to be able to
wink can wink. Create a clip on the K2 media client and wink it to a
non-SmartBin using Aurora Edit. Likewise, create a Aurora Edit clip and wink
it to a K2 media client non-SmartBin.
3. SmartBins:
4 October 2010
Aurora Edit Installation Guide
135
Aurora Edit Security