apache > db
Apache DB Project
Font size:      

Client/Server Environment

Client/Server Environment

In this example, Derby is running in a user-designed application server. Derby provides the user authentication, not the application server. The server is running in a secure environment, the application server encrypts the passwords, and a database administrator is available. The administrator configures security using system-level properties in the derby.properties file and has protected this file with operating system tools. Derby connects to an existing LDAP directory service within the enterprise to authenticate users.

The default access mode for all databases is set to fullAccess (the default).

The derby.properties file for the server includes the following entries:

# turn on user authentication
# set the authentication provider to an external LDAP server
# the host name and port number of the LDAP server
# the search base for user names
# explicitly show the access mode for databases (this is default)

With these settings, all users must be authenticated by the LDAP server in order to access any Derby databases.

The database administrator has determined that one database, accountingDB, has additional security needs. Within a connection to that database, the database administrator uses database-wide properties (which override properties set in the derby.properties file) to limit access to this database. Only the users prez, cfo, and numberCruncher have full (read-write) access to this database, and only clerk1 and clerk2 have read-only access to this database. No other users can access the database.

    'derby.database.defaultAccessMode', 'noAccess')
    'derby.database.readAccessUsers', 'clerk1,clerk2')

The database administrator then requires all current users to disconnect and re-connect. These property changes do not go into effect for current connections. The database administrator can force current users to reconnect by shutting down the database

Previous Page
Next Page
Table of Contents