Percona Server for MongoDB 7.0.31-17 (2026-03-30)¶
Installation Upgrade from MongoDB Community
Percona Server for MongoDB 7.0.31-17 is an enhanced, source-available, and highly-scalable database that is a fully-compatible, drop-in replacement for MongoDB Community Edition.
Percona Server for MongoDB 7.0.31-17 includes the improvements and bug fixes of:
It supports protocols and drivers of MongoDB Community 7.0.31.
Release highlights¶
Enhanced LDAP authentication caching¶
To provide better parity with MongoDB Enterprise and improve performance in high-scale environments, we have introduced two new configuration parameters for LDAP user caching. These options allow administrators to fine-tune how and when cached user information is refreshed, reducing unnecessary overhead on LDAP servers while ensuring security data remains current.
New parameters
ldapUserCacheRefreshInterval: The ldapUserCacheRefreshInterval parameter sets the frequency (in seconds) at which the server proactively refreshes cached user information from the LDAP server. This allows the system to update permissions and group memberships in the background before the cache entry expires. For more detailed information, refer to MongoDB server parameters.
ldapShouldRefreshUserCacheEntries: The ldapShouldRefreshUserCacheEntries parameter is a toggle that determines the cache renewal strategy. For more detailed information, refer to MongoDB server parameters.
-
If set to true: The server will use the
ldapUserCacheRefreshIntervalto proactively update entries. -
If set to false: The server will wait for the
ldapUserCacheInvalidationInterval(already supported in PSMDB) to pass before clearing and refetching the entry on the next login attempt.
Changelog¶
Improvements¶
PSMDB-1947: To provide better parity with MongoDB Enterprise and improve performance in high-scale environments, we have introduced two new configuration parameters for LDAP user caching. These options allow administrators to fine-tune how and when cached user information is refreshed, reducing unnecessary overhead on LDAP servers while ensuring security data remains current.
Bugs¶
PSMDB-1998: Resolved an issue where user authentication was stuck indefinitely when the LDAP server was unreachable. Timeouts are now applied to LDAP connections to avoid blocking and ensure more reliable authentication.