User manual GRASS VALLEY AURORA EDIT SECURITY APPLICATION NOTE 01-2011

[. . . ] You create groups of users, such as editors, producers, and interns, and set permissions for each group. You control access to subbranches of the bin tree for users and groups. the administrator has exclusive access to a tool in the top-level bin that allows the setting of permissions on the bin-tree root. At all levels of bins (as a feature of Active Directory), you control who can control access. Technical Background As part of its open architecture, the Aurora suite of products stores media on Windows-compatible file system volumes, notably the Grass Valley K2 SummitTM shared storage system. [. . . ] · Assuming inheritance isn't blocked, users who have W permission within a bin can create working sub-bins to an arbitrary depth. note that the bin, group, and user designations in this example are not imposed by Aurora edit; these entities are chosen by the user. Active Directory, and in turn Aurora edit, support whatever schema your organization requires. Security in action: in the screen capture below, user Joe intern, a member of the interns group, has attempted to delete a subclip within the Monday bin and been denied permission. 2 www. grassvalley. com AurorA Edit SEcurity Setting Permissions the most direct way to set permissions on an object in the bin tree is through Aurora edit, as shown in the examples below. Aurora edit passes the Windows Security property sheet (the Security tab you would see for a file in Windows explorer) to the user within the bin's properties dialog. Here we see that user Joe edit has been explicitly granted full control on a bin. Another entry on the same bin shows that the group interns has inherited read-only permission. (inheritance is indicated by the gray-shaded checkbox. ) the assets in Aurora edit's bin tree associate with folders in the file system. As an alternative to setting permissions with Aurora edit, you can set permissions directly on the associated folders using, for example, Windows explorer, or any administrative application. typically, during configuration, organizations establish an inheritance and group hierarchy for assets and users such that permissions do not require constant management; the desired access control happens automatically because of where the asset is located and who is using it, not because every new asset has had its permissions set manually. www. grassvalley. com 3 AurorA Edit SEcurity Configuration careful configuration is the key to carefree enjoyment of Aurora edit Security. inheritance and grouping provide nearly automatic access control. the Aurora edit installation manual details how to set up the security option. Briefly, you would follow these steps: Design a security schema appropriate for your organization. this is a hierarchy similar to that shown in the example table to describe which users and groups have access to which assets. this can be very simple, with just a few users and groups, or very complex, with hundreds of users and groups. Active Directory can support arbitrarily intricate hierarchies. Before configuring security on Aurora edit, most organizations already have a domain schema designed and supported by their it departments. Establish an Active Directory domain and join the Aurora equipment to the domain. organizations often already have configured domains that may consist of AD trees or forests, so this step reduces to the straightforward task of joining the Aurora machines to the domain. if the infrastructure does not already exist, a domain and domain controller can be configured for the work cluster that uses Aurora. Modify service users as necessary for the domain. Depending on how the Aurora equipment was originally deployed, i. e. , depending on whether it was born onto a workgroup or a domain, several services, e. g. , SmartBins, Advanced encoder, and conform Server, may require a user change. [. . . ] Using the Aurora edit Security feature, you can militate against these misfortunes. to address the large and small scope of similar concerns, Aurora edit Security provides fine-grain, scalable, Windows Active Directory-compatible control of Aurora assets. please refer to the Aurora Edit and LD Installation Manual for more detail about the Security feature and its configuration. SALES Local and regional sales contacts can be found by visiting www. grassvalley. com/sales SuPPort Local and regional support contacts can be found by visiting www. grassvalley. com/support © Copyright 2011 Grass Valley USA, LLC. Grass Valley, Aurora, and K2 Summit are trademarks of GVBB Holdings S. a. r. l. [. . . ]