3.2
Table Of Contents
- Title Page
- Contents
- Using This Guide
- Getting Started with the Interplay | Administrator
- Database Settings
- Creating an Interplay Database
- Interplay Databases, Folders, and Files
- Creating and Restoring Database Backups
- Types of Interplay Administrator Backups
- Recommendations for Backup Configuration
- Setting the Number of Database Backups to Keep
- Scheduling Automatic Database Backups
- Starting a Backup Manually
- Using an Archiving Tool for Backup
- Restoring an Earlier Version of a Database
- Performing a Partial Restore of an Interplay Production Database
- Creating a Metadata-Only Backup for Customer Support
- Performing a Consistency Check
- Viewing Database Information
- Locking and Unlocking Databases
- Managing Databases: Deactivating, Activating, and Migrating
- Moving a Database to Another Server (Non-Clustered Systems)
- Moving a Database and Users to Another Server (Non-Clustered Systems)
- Moving a Database to Another Server (Clustered Systems)
- Moving a Database and Users to Another Server (Clustered Systems)
- Moving a Database Under Low Disk Space Conditions
- Renaming a Database
- Running Database Maintenance Tools
- Identifying the Root Folder of the Interplay Server Database
- Server Settings
- User Management
- Understanding the Central Configuration Server
- Adding Users to a Central Configuration Server
- Setting User Authentication Providers and Importing Users
- Managing Users, User Groups, and User Rights
- Understanding Default User Groups, Users, and Roles
- Adding User Groups
- Adding Users Manually
- Viewing and Setting Attributes
- Understanding Standard Roles and Default Rights
- Viewing and Changing Roles
- Viewing and Setting Authentication Providers for Individual Users
- Deleting Users and User Groups
- Removing Users from User Groups
- Managing Database Roles
- Guidelines for User Management
- Site Settings
- Defining Property Layouts
- Setting the Resolutions Available for Display
- Creating Custom Properties
- Configuring Remote Workgroups
- Configuring Categories
- Setting Server Hostnames and the Workgroup Name
- Interplay Media Services View
- Interplay Transfer Status View
- Interplay Transfer Settings View
- Workgroup Transfer Presets View
- Specifying Remote Servers for Asset Tracking
- Specifying Archive Settings
- Setting the Ownership for New Database Folders
- Enabling Interplay Synced Projects
- Setting Options for Deletion
- Viewing and Setting the Metadata Override Status
- Production Engine Bus Connector
- Application Settings
- Application Database Settings View
- Setting Options in the Editing Settings Tab
- Setting Audio Mixing Defaults for Access, Assist, and MediaCentral | UX
- Sending a Source to Playback in Interplay Assist
- Setting the Shotlist Start Timecode for Interplay Access and Interplay Assist
- Setting an Automatic Timeout for Interplay Assist and Avid Instinct
- Configuring the Frame Locators Display
- Configuring the Restrictions Display
- Media Composer | Cloud Settings
- Setting Instinct/Assist User Options
- Pro Tools Plug-Ins Settings
- Application Database Settings View
- Interplay Services
- Troubleshooting
- Reuniting a Split Database
- Installed Components and Services
- Interplay Engine Configuration Files
- Valid and Invalid Characters in Interplay
- System Metadata Properties
- Server Error Codes
- Consistency Check Codes
- Index
Configuring Client Access
275
The “name” attribute specifies the name of the database. This name must be the same as the
name of the database configured in the Active Database List through the Interplay Administrator.
If a database is not in the Active Database List, it cannot be made visible by specifying its name
in <project> token either. You can also use the “*” as a wildcard character representing all
databases in the Active Database List.
The “access” attribute specifies the type of access for the database. If it is set to “allow,” clients
can see the database in the database browser and are allowed to access it. If the attribute is set to
“deny,” the database is not accessible and is not even visible to the clients. By default, everything
is set to “deny.”
With the <user> token, you specify which users are allowed to connect to a database. As with the
<project> token, the “name” and “access” attributes can also be used here. The name attribute is
the name of a user in the database. The “name” attribute supports the “*” (wildcard) value
representing all users.
Database and user settings are inherited from the parent node in the token tree if the settings are
not specified on the current level. This allows you to specify access permissions for all databases
on a server, or even for all servers.
The additional attribute “emptypassword” is supported for the <project> and <server> tokens.
This attribute can be set to the value “allow” or “deny.” If set to “deny,” then all connection
attempts by a user with no password specified are refused by the server or the database,
respectively. By default, whenever you create a user in an Interplay database, the password is set
to empty. Avid highly recommends setting this value to “deny” for security reasons.
Following are some examples illustrating the configuration of database and user access.
Example 1:
<XML>
<server name="WGSERVER">
</server>
</XML>
The server WGSERVER is visible to the outside, although no databases are accessible.