Skip to content
Percona Documentation
Rate this page
☆ ☆ ☆ ☆ ☆
Thanks for your feedback
Thank you! The feedback has been submitted.

Get free database assistance or contact our experts for personalized support.

Get help from Percona

Percona Server for MongoDB 7.0.31-17 has been released

Percona Server for MongoDB 7.0.31-17 has been released on March 30, 2026.

Try it out using the Quickstart guide.

This release provides the following improvements:

  • 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 ldapUserCacheRefreshInterval to 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.

  • Implement LDAP user cache refresh options

    In addition to introducing these new LDAP cache parameters, this release enables more predictable and controllable cache behavior in production deployments. You can now configure ldapUserCacheRefreshInterval and ldapShouldRefreshUserCacheEntries through the standard mongod configuration file or startup parameters, and combine them with the existing ldapUserCacheInvalidationInterval to balance authentication latency against the freshness of user and group information.

Learn more about this release in Percona Server for MongoDB 7.0.31-17 release notes.