This procedure requires a system with multiple databases and some
administrative resources.
- Configure security features as system-level properties.
- Provide administrative-level protection for the
derby.properties file
and Derby databases. For
example, you can protect these files and directories with operating system
permissions and firewalls.
- Turn on user authentication for your system. All users must provide
valid user IDs and passwords to access the
Derby system. Use NATIVE
authentication (or, alternatively, LDAP or a user-defined class).
Important: It is also strongly recommended that production
systems protect network connections with SSL/TLS.
- Configure fine-grained user authorization (SQL authorization) for
your databases.
- Configure Java security for your environment.
The following figure shows some of the
Derby security mechanisms at
work in a client/server environment. User authentication is performed by
accessing an LDAP directory service. The data in the database is not encrypted
in this trusted environment.
Figure 1. Using an LDAP directory service in a trusted
environment
