Database Server Permissions - Novell ADMINSTUDIO 9.5 User Manual

Database Server Permissions

In order to operate some AdminStudio tools, AdminStudio users require specific database permissions.
Depending upon the type of user, you may wish to be more selective in the permissions you assign to these users.
If you have AdminStudio Enterprise Edition, you can assign permissions to individual users using the Role
functionality in AdminStudio Enterprise Server, as described in
Permissions. Otherwise, you can provide more selective restrictions at the database server level using the
information in the following table, AdminStudio Database Server Permissions.
Every AdminStudio user will need at a minimum read privilege to every table in the Application Catalog. The
minimum permissions are described below, based upon the type of operation you want the user to perform.
Table 6-84 • AdminStudio Database Server Permissions
Type
General User
Administrative
Process
Import Process
Validation Process
Dependency
Scanning Process
AdminStudio 9.5 User Guide
Description
General administrative processes cover a range of activities such as adding groups,
moving packages around, adding comments, updating extending attributes, etc. For
example, these tables include cstblPackage, cstblGroups, and
cstblGroupPackages Any Application Catalog table which is not referenced
explicitly in the discussion for the other AdminStudio processes should be
considered a general user administrative table.
Most AdminStudio users should have write access to these tables.
The user importing MSI packages, merge modules, or just about anything will
require write access to a significant set of Application Catalog tables depending on
the type of import. For example:
•
MSI package
Catalog tables with a csmsi prefix are populated.
•
Merge modules—For merge module import operations, the csmsm prefixed
tables are used.
•
Patches—For patch import operations, the cspch prefix tables are used.
• OS snapshots—For OS snapshot import operations, the osc prefix tables are
used.
Occasionally, the Import process will need to create new tables in the Application
Catalog to support the import of custom table data. Either the necessary server
privileges need to be given for these users, or the import of custom table data needs
to be disabled within the Application Manager Options dialog box.
For this process, the user will need to be able to write entries into the
cstblValidationResults and cstblValidationConfiguration tables.
For this process, the user will need to be able to write entries into the
cstblPackageExeDependencies table.
ADS-0950-UG00
Chapter 6: Managing Application Catalog Databases
AdminStudio and Workflow Manager Roles and
file—For MSI package file import operations, those Application
Reference
387