IBM Db2 Big SQL 7.1.0

Native Db2 Big SQL

Use these procedures to set up authorization using native Db2 Big SQL security features.

Authorization of Db2 Big SQL objects
Authorization of Db2 Big SQL objects is controlled at several layers. The Db2 Big SQL permissions are maintained within the Db2 Big SQL catalog tables.
Database authorization
Authorization is the process where the database manager gets information about the authenticated user. Part of that information is determining which database operations the user can perform and which data objects a user can access.
Default privileges granted on the bigsql database
When you install IBM Db2 Big SQL, a default database is created for you. The default database level authorities and default object level privileges are granted to you within that database.
Row and column access control (RCAC) overview
Row and column access control (RCAC) can be used together with the Db2 Big SQL Ranger plugin to control authorizations on Db2 Big SQL objects, thereby providing an optimal security solution. Row and column access control is sometimes referred to as fine-grained access control or FGAC. RCAC controls access to a table at the row level, column level, or both. RCAC can be used to complement the table privileges model.
Authorization properties for the LOCATION clause
Some configuration properties can be modified after you install Db2 Big SQL to validate your authorization to use the LOCATION clause, or to enforce the requirement that the LOCATION clause can be provided in conjunction with the EXTERNAL clause only. This ensures that the DROP command does not accidentally drop data that does not reside in the distributed file system warehouse directory.
Importing authorization to Db2 Big SQL authorization
When HDFS and HIVE authorization are enabled in the Hadoop cluster, they can be mapped manually to native Db2 Big SQL authorizations.

Parent topic: Authorization