Firebird Documentation Index → Firebird 3.0.6 Release Notes → Security |
Table of Contents
Security improvements in Firebird 3 include:
Firebird now supports an unlimited number of security databases. Any database may act as a security database and can be a security database for itself.
Use databases.conf
to configure a non-default security database. This example
configures /mnt/storage/private.security.fdb
as the security database for
the first and second databases:
first = /mnt/storage/first.fdb { SecurityDatabase = /mnt/storage/private.security.fdb } second = /mnt/storage/second.fdb { SecurityDatabase = /mnt/storage/private.security.fdb }
Here we use third database as its own security database:
third = /mnt/storage/third.fdb { SecurityDatabase = third }
The value of the SecurityDatabase parameter can be a database alias or the actual database path.
To start using a separate, non-default security database, the first step is to create it, unless it already exists. An embedded isql connection is used:
> isql -user sysdba SQL> create database '/mnt/storage/private.security.fdb';
Now connect to any database which will be served by the security database you are currently preparing, in order to create its SYSDBA user:
SQL> connect first; SQL> create user sysdba password 'sysdba-in-private-security-password'; SQL> commit; SQL> exit;
Firebird Documentation Index → Firebird 3.0.6 Release Notes → Security |