Description: In an embedded environment, typically there is only one database per system and there are no administrative resources to protect databases.

# Configuring security in an embedded environment

In an embedded environment, typically there is only one database per system and there are no administrative resources to protect databases.

To configure security in an embedded environment:

1. Encrypt the database when you create it.
2. Configure all security features as database-level properties. These properties are stored in the database (which is encrypted). See Tuning Java DB.
3. Turn on protection for database-level properties so that they cannot be overridden by system properties by setting the derby.database.propertiesOnly property to TRUE.
4. To prevent unauthorized users from accessing databases once they are booted, turn on user authentication for the database and configure user authorization for the database.
5. If you are using Derby's built-in users, configure each user as a database-level property so that user names and passwords can be encrypted.

Parent topic: Configuring security for your environment
Related concepts
Working with user authentication
User authorizations
Related tasks
Configuring security in a client/server environment