# R1924 (22-Feb-2026) This release introduces new features as below: ### **What's New** **Enhanced Bot Statistics:**\ Bot statistics now include both **Discovery and Provisioning metrics**, providing improved visibility into bot performance and operational activities. **CA Connector Test and Save Validation:**\ Administrators can now test CA connector configurations before saving them, ensuring the connectors are correctly configured and reducing integration errors. **Product-Based Custom Field Mapping:**\ Custom fields can now be mapped directly to specific certificate products, allowing organizations to capture product-specific information during certificate request workflows. **Improved Custom Field Display for PKI Products:**\ Custom fields configured during PKI product profile creation are now displayed under **Certificate Information**, while the remaining fields continue to appear under **Additional Information**, maintaining existing behavior. **Default Custom Fields and Auto Refund Configuration:**\ Custom fields and the **Auto Refund within 30 days of certificate revocation** option are now enabled by default for all self-onboarded accounts. **Agent-Based and Agentless Bot Differentiation:**\ The Bot Configuration page now clearly differentiates between **Agent-Based and Agentless Bot approaches**, improving clarity during bot setup and configuration. **Technical Point of Contact Role Definition:**\ The responsibilities and role of the **Technical Point of Contact (TPOC)** are now clearly defined across the platform for better operational management. **Euro Currency Support:**\ CERTInext now supports **Euro (€) currency**, allowing organizations to manage billing and transactions in European currency. **CERTInext Bot as a Service:**\ The CERTInext Bot now runs as a **system service**, ensuring continuous execution and improved operational reliability. ### **Enhancements** **Integration Execution via Bot:**\ Integrations such as **F5, AWS, and other supported platforms** now operate through the CERTInext Bot instead of directly through the CERTInext application, improving network isolation and deployment flexibility. **Bot Log Visibility in the UI:**\ The CERTInext Bot now pushes log files to the platform, allowing administrators to view and monitor bot logs directly within the user interface. **Improved Bot Data Storage Location:**\ Bot-related data, including the SQLite database and operational files, are now stored under **Program Data** instead of user profile App Data, ensuring better system stability. **Placeholder and Field Text Improvements:**\ All placeholders across the platform have been reviewed and updated to improve clarity and consistency. **Server-Side Validation Enhancements:**\ Comprehensive server-side validations have been implemented to ensure improved data accuracy and platform reliability. **Field Length Validation Improvements:**\ Proper field length validations have been introduced wherever applicable to prevent data inconsistencies. **Removal of CommServer Dependency:**\ The platform no longer depends on CommServer APIs. Email and SMS services are now handled internally within CERTInext. **Removal of IP Server Dependency:**\ Dependency on IP Server APIs has been removed, with the related implementations now handled internally. ### **Security Updates** **VAPT Issue Resolution:**\ All vulnerabilities identified during the **Digital Age VAPT assessment** have been addressed to improve platform security. **Environment Variable and Log4j Improvements:**\ Environment variable handling and Log4j configurations have been reviewed and implemented across all projects to strengthen platform security. **Cloudflare Turnstile Implementation:**\ Cloudflare Turnstile has been implemented to replace **Google reCAPTCHA**, improving privacy compliance and authentication security. ### **Certificate Lifecycle Enhancements** **Suspend and Revoke for CA and End Entity Certificates:**\ Administrators can now suspend and revoke both **Certificate Authority certificates and End Entity certificates**, enabling better certificate lifecycle management. ### **Dynamic Application Behavior for On-Premise Deployments** **Back-office Finance Handling:**\ Back-office systems now dynamically handle finance and account-related features based on deployment configurations. **Self-Onboarding Configuration:**\ Self-onboarding functionality can now be dynamically enabled or disabled based on deployment settings. **Dynamic Login Page Banner:**\ The login screen banner content can now be configured dynamically depending on the deployment environment. **Dashboard Configuration Improvements:**\ Dashboard components now dynamically adapt to handle **pricing, domains, organizations, and related configurations**. **Configurable CAPTCHA on Login Page:**\ Image-based CAPTCHA can now be enabled on the login page based on deployment configuration. **Group-Level Domain and Organization Management:**\ Domains and organizations are now handled within groups to provide improved hierarchical management. **Finance Handling Across Platform Components:**\ Financial workflows are now consistently handled across **the application, APIs, and supported protocols**. **CLM Module Enabled by Default:**\ The Certificate Lifecycle Management (CLM) module is now enabled by default in on-premise deployments. **Enhanced Certificate Request Workflow:**\ The certificate request workflow now supports **KYC document uploads, Skip CSR option, and DNS type selection (Internal or External)** for improved flexibility. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.certinext.io/documentation/release-notes/r1924-22-feb-2026.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.