Derby and Security

Derby can be deployed in a number of ways and in a number of different environments. The security needs of the Derby system are also diverse.

Derby supplies or supports the following optional security mechanisms:

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. Example of using an LDAP Directory Service in a trusted environment.
This figure shows user
authentication from an LDAP directory service to the Derby engine and user
authorization to read and write data. The Derby database is a trusted environment
and the data is not encrypted.
The following figure shows how another Derby security mechanism, disk encryption, protects data when the recipient might not know how to protect data. It is useful for databases deployed in an embedded environment.
Figure 1. Example of using disk encryption to protect data.
This figure shows disk
encryption between the Derby engine and the database.
Related concepts
Creating, dropping, and backing up databases