Other Topic Library Versions

FTP and media access security

The following systems host the K2 FTP interface:
  • A stand-alone K2 system.
  • A K2 Media Server that takes the role of FTP server

The way in which the K2 FTP interface applies media access security is explained in this section.

The K2 FTP interface uses the credential information for the current FTP session logon and checks it against the access control list for a K2 bin. This is the access control list that you set up through the Organize Bins dialog box in AppCenter. Any media access related operations such as get, put, dir, rename and delete are checked against the FTP session’s logon credentials to access the media. For example, if an FTP session is denied access to List Bin Contents for bin A, then the session can not initiate a dir operation on bin A to list the contents of the bin. Furthermore, the session can not transfer clips into bin A using the put operation.

For the purpose of legacy support with older Profile systems, accounts for user movie or user mxfmovie are provided on the K2 system. There is also a video_fs account for Mac/FCP access. These accounts are automatically set up when you install K2 software version 3.2 or higher. Do not restrict access for these accounts. If your security policy requires restricting access to these accounts, contact Grass Valley Support.

On a K2 SAN, authentication takes place on the K2 Media Server. Setting up FTP security for specific local users and groups is not supported on a K2 SAN, with the exception of the local movie and mxfmovie accounts. However, you can set up FTP security for domain users and groups.


Copyright © 2019 Grass Valley Canada. All rights reserved. K2 Summit 10.1.2 gvtp_20191213_00:21:37