|
Security is a database property that requires a user to provide a user name and password to access the database. By default, database security is turned off.
Database security can be turned on through PCC or by executing an SQL statement. Once enabled, you may create groups and users and assign permissions to them. Permissions can include database rights, table rights, and column rights within tables.
When you turn security on or off, the Master user must have only one connection open and must be the only user connected.
As soon as you turn security on for the first time, only the Master user can access the database. The Master user password, as with all Pervasive PSQL passwords, is case sensitive.
Caution
If you turn on security, be sure to specify a password with a significant length. Do not leave the password field blank because doing so creates a major security risk for your database.
See Pervasive PSQL Security chapter in Advanced Operations Guide for additional information about security.
This section contains step-by-step tasks pertaining to security. The tasks are divided into the following categories:
|
Category
|
Description
|
|---|---|
|
Orient you to the overall use of security
|
|
|
Apply to security policies for the transactional interface
|
|
|
Apply to creating users and groups
|
|
|
Apply to assigning permissions to users and groups
|
|
|
Encryption Tasks
|
Apply to data encryption
See Data Encryption in Advanced Operations Guide.
|
To log into a database using PCC when you are already logged into that database as another user
Note
As the Master user, logging in as another user can aid you in testing the more restrictive permissions you have assigned this user.
Name reflects the name of the user currently logged in to the database. If the database does not have security enabled, name is Master. Name may also be Master if the current user is logged in as Master.
Any nodes expanded for the database are collapsed.
To turn on security using Pervasive PSQL Explorer
If the database resides on a remote machine, you must provide a user name and password of an administrator or of a member of the Pervasive_Admin group for the remote machine. The user name and password is not required if the database resides on the local machine to which you are logged in (and the local machine is not running Terminal Services).
Turning on security prevents all users from accessing the database unless they login to it using a valid database user name and password. User names and passwords cannot be set up until security is turned on, so the database will be inaccessible to each user for the period of time until you have set up a user account for that user.
Database security is now on and you are logged in as the Master user. For instructions on creating database user accounts, see User and Group Tasks .
To turn on security using SQL
You must be logged into the computer as an administrator or as a member of the Pervasive_Admin operating system security group.
Turning on security prevents all users from accessing the database unless they login to it using a valid database user name and password. User names and passwords cannot be set up until security is turned on, so the database will be inaccessible to each user for the period of time until you have set up a user account for that user.
The Select Database dialog box appears.
See also SET SECURITY in SQL Engine Reference.
To turn off security using Pervasive PSQL Explorer
You must be logged into the computer as an administrator or as a member of the Pervasive_Admin operating system security group.
Caution
Turning off security allow all operating system users to access the database through the relational and transactional interfaces if database security is Mixed or Database mode.
Database user names, passwords, and permissions are retained but not used if security is turn off. If security is re-enabled, the previous user names, passwords, and permissions take effect again. (An exception is the Master user. The Master password is not retained nor re-applied.)
To turn off security using SQL
Caution
Turning off security allow all operating system users to access the database through the relational and transactional interfaces if database security is Mixed or Database mode.
Database user names, passwords, and permissions are retained but not used if security is turn off. If security is re-enabled, the previous user names, passwords, and permissions take effect again. (An exception is the Master user. The Master password is not retained nor re-applied.)
The Select Database dialog appears.
See also SET SECURITY in SQL Engine Reference.
To set or change the security policy for a database
Caution
Changing security policy for a database may prevent current users from accessing the database, if security is turned on and the given users do not have equivalent user accounts and rights under the new security policy.
See also the chapter Pervasive PSQL Security in Advanced Operations Guide.
Caution
If your database has security turned on and you change from Classic security policy to Mixed or Database, all users are prevented from accessing the database until you create database user accounts and privileges for them.
To use an existing database, including the pre-defined DefaultDB, with your Pervasive PSQL files
If your files are spread over many directories, specify a high-level directory that they all have in common. You can specify a root level if necessary, but doing so includes in the database all Pervasive PSQL+ files at the root level and its subordinate directories.
You do not need to enter every directory, just the lowest level directory that is common to all Btrieve files you want to include in the database.
To create a new group using Pervasive PSQL Explorer
Note that you cannot add a group to another group.
To create a new user using Pervasive PSQL Explorer
Passwords are case sensitive. For a list of database object lengths and invalid characters, see Identifier Restrictions by Identifier Type in Advanced Operations Guide..
Click
for Group, then click the desired group in the list.
To assign a user to a group using Pervasive PSQL Explorer
Note that a given user cannot be a member of more than one group. All users in a group have exactly the permissions defined for that group. You cannot grant or revoke individual permissions for a user who is a member of a group.
for Group, then click the desired group in the list.
To delete a group or user using Pervasive PSQL Explorer
Note that a group can be deleted only if no users are assigned to it.
To work with groups and users using SQL
The Select Database dialog box appears.
Refer to the following statements in SQL Engine Reference:
To assign permissions for a group using Pervasive PSQL Explorer
Note
Permissions on the Database tab override permissions on the Table tab.
A check mark indicates that the permission applies.
To assign permissions for a user using Pervasive PSQL Explorer
Note
You cannot assign specific permissions to a user if the user is a member of a group. The permissions of the group apply to the user.
Permissions on the Database tab override permissions on the Table tab.
A check mark indicates that the permission applies.
To assign permissions to all users using Pervasive PSQL Explorer
Note
Permissions on the Database tab override permissions on the Table tab.
A check mark indicates that the permission applies.
To assign permissions for a group or user using SQL
The Select Database dialog box appears.
In SQL Engine Reference, see the following:
|
Chapter contents
Prev topic: Triggers, Stored Procedures, User-defined Functions, and Views
|