Understanding and Managing Database Credentials in ekp.properties

Applicable Product:

PeopleFluent Learning

Applicable Release:

All Versions

Overview

The ekp.properties file contains critical configuration settings that allow the LMS to connect to its database. This article explains how database credentials are defined, how plain text and encrypted passwords are used, and what administrators need to be aware of when maintaining or updating these values.

Key Properties Involved

The database connection is configured using the default connection pool, including:

default.driverName
default.connectURL
default.dbType
default.user
default.password
default.encryptedPassword

Example:

default.user=ndadmin
default.password=*******
#default.encryptedPassword=0D41A73405A42895

Plain Text vs Encrypted Passwords

default.password
- Stores the plain text database password
- Used during initial setup or special operations (e.g., license change)
default.encryptedPassword
- Stores an encrypted version of the database password
- Overrides default.password when enabled
- Encryption is license-dependent

If default.encryptedPassword is present and active, the LMS will ignore default.password.

Best Practices

Use encrypted passwords in production environments
Keep plain text passwords only temporarily
Ensure only one password method is active at a time
Restrict access to ekp.properties at the OS level

Common Mistakes to Avoid

Leaving both default.password and default.encryptedPassword active
Copying encrypted values from another environment or license
Introducing spaces or line breaks when editing values

Summary

Database access depends entirely on correct credentials in ekp.properties
Encrypted passwords are preferred but license-dependent
Proper handling prevents startup and connectivity issues