Access control, Overview, Summary – Grass Valley iControl V.4.43 User Manual
Page 307

Access Control
This chapter describes iControl’s mechanism for implementing access control.
Summary
Configuring LDAP on an Application Server
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Creating, Modifying, and Removing Users
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Resetting the Admin (super) User Password
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Overview
Each iControl Application Server has a default user defined—the admin user. This user has the
role of super assigned to it, which means that anyone who logs in as admin has access to
everything in the domain.
The default admin user also has a default password, which is also
admin
. This password can be
changed. You might want to do this, for example, at the initial setup of an Application Server
to improve security. The
admin
user/password can also be restored to their original state if
accidentally deleted. For more information about resetting the user password, see
the Admin User Password on an iControl Application Server"
As shipped, an Application Server can be used by any user on the same network to open any
program, view any pages, modify any device parameters, and so on. Access control, also called
user authentication or privilege management, allows you to make iControl system resources
(such as cards, services, and Web pages) available only to designated users.
While not meant to be a foolproof security system, access control allows you to manage users
in a way that minimizes the potential for errors. For example, you can prevent a guest user