# Announcements ## 2024 -------------------------------------------------------------------------------- title: "LinkedIn Migrating to OpenID Connect" last_updated: "2026-03-18T07:41:08.535Z" source: "https://docs.catalyst.zoho.com/en/announcements/2024/linkedin-announcement/" service: "All Services" related: - Configuring LinkedIn Identity Provider (/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-linkedin-social-login/) -------------------------------------------------------------------------------- {{% divtag class="dF align-center gap-10"%}} # LinkedIn Migration to OpenID Connect from OAuth {{%/divtag%}} LinkedIn has {{%link href="https://www.linkedin.com/developers/news/featured-updates/openid-connect-authentication" %}}announced{{%/link%}} their decision to migrate from {{%badge%}}OAuth{{%/badge%}} protocols to {{%badge%}}OpenID Connect{{%/badge%}} protocols on **January 10, 2023**. As per their announcement, they have implemented this change to provide an additional identity layer of security over the {{%badge%}}OAuth{{%/badge%}} protocols. This change will affect our users who have implemented the LinkedIn Identity Provider's Authentication for their Catalyst application. The new scopes that you will be configuring in the {{%link href="https://www.linkedin.com/developers/" %}}LinkedIn developer portal{{%/link%}} are listed below. <table class="content-table"> <thead> <tr> <th class="w25p">Scope</th> <th class="w75p">Purpose</th> </tr> </thead> <tbody> <tr> <td>{{%badge%}}openid{{%/badge%}}</td> <td>To indicate the application wants to use OIDC to authenticate the member.</td> </tr> <tr> <td>{{%badge%}}profile{{%/badge%}}</td> <td>To get the member's lite profile including their id, name, and profile picture.</td> </tr> <tr> <td>{{%badge%}}email{{%/badge%}}</td> <td>To get the member's email address</td> </tr> </tbody> </table> For more information on {{%badge%}}OpenID Connect{{%/badge%}} protocols, visit their {{%link href="https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin-v2" %}}official documentation{{%/link%}}. In light of this new change, we urge you to regenerate your authentication tokens using {{%badge%}}OpenID Connect{{%/badge%}} protocols. The steps to generate {{%badge%}}ClientID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} tokens can be found our {{%link href="/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-linkedin-social-login" %}}help documentation{{%/link%}}. LinkedIn has additionally stated that if their end-users have implemented LinkedIn identity providers for their applications before **August 2023**, they will continue to support {{%badge%}}OAuth{{%/badge%}} and {{%badge%}}OpenID Connect{{%/badge%}} protocols for them for an unspecified extended time period. However, given the ambiguity on it's deprecation date, we urge you to to migrate your projects that use LinkedIn signups from {{%badge%}}OAuth{{%/badge%}} protocols to {{%badge%}}OpenID Connect{{%/badge%}} protocols as soon as possible. <br /> -------------------------------------------------------------------------------- title: "Node.js Runtime Updates" last_updated: "2026-03-18T07:41:08.535Z" source: "https://docs.catalyst.zoho.com/en/announcements/2024/nodejs-announcement/" service: "All Services" related: - Catalyst Language Runtime Policy (/en/serverless/help/functions/runtime-support/) - Node.js Runtimes (/en/serverless/help/functions/stack/#nodejs-functions) - Upgrading Function Runtimes (/en/serverless/help/functions/implementation/#update-or-download-a-function) -------------------------------------------------------------------------------- {{% divtag class="dF align-center gap-10"%}} # Node.js v10 and Node.js v12 Runtime Updates from Catalyst {{%/divtag%}} As per the {{%link href="https://nodejs.org/en/about/previous-releases" %}}official announcements{{%/link%}} made by the Node.js community, they have completely stopped the support of Node.js {{%badge%}}v10{{%/badge%}}, and {{%badge%}}v12{{%/badge%}} runtimes. Following suit, Catalyst announced the EOL status and slated the retirement dates for these runtimes on the following dates: - {{%link href="/en/release-notes/all/#2022---november" %}}Node.js {{%badge%}}v10{{%/badge%}}{{%/link%}} - Deprecation date - **November 2022** - Retirement date - **January 31, 2023** - {{%link href="/en/release-notes/all/#2022---march" %}}Node.js {{%badge%}}v12{{%/badge%}}{{%/link%}} - Deprecation date - **March 2022** - Retirement date - **July 31, 2023** As per {{%link href="/en/serverless/help/functions/runtime-support/" %}}Catalyst's language runtime policy{{%/link%}}, both Node.js {{%badge%}}v10{{%/badge%}} and Node.js {{%badge%}}v12{{%/badge%}} have reached the {{%link href="/en/serverless/help/functions/runtime-support/#phase-4-end-of-support" %}}End of Support{{%/link%}} stage. We urge our users with applications or microservices in these runtimes to migrate their codebases to the newer runtimes. Catalyst currently offers support in the following {{%link href="/en/serverless/help/functions/stack/#nodejs-functions" %}}Node.js runtimes{{%/link%}}: * Node.js {{%badge%}}v14{{%/badge%}} * Node.js {{%badge%}}v16{{%/badge%}} * Node.js {{%badge%}}v18{{%/badge%}} If you do decide to continue coding your applications using the deprecated runtimes, you do so at your own risk and as of this announcement date, Catalyst has effectively terminated support for Node.js {{%badge%}}v10{{%/badge%}} and Node.js {{%badge%}}v10{{%/badge%}} runtimes. You can {{%link href="/en/serverless/help/functions/implementation/#update-or-download-a-function" %}}upgrade your function's runtime{{%/link%}} and {{%link href="/en/serverless/help/functions/implementation/#code-editor" %}}update your code{{%/link%}} directly in the console. <br /> -------------------------------------------------------------------------------- title: "Deprecation of ZCQL API Version v1 " last_updated: "2026-03-18T07:41:08.535Z" source: "https://docs.catalyst.zoho.com/en/announcements/2024/zcql-deprecation-announcement/" service: "All Services" related: - ZCQL v2 Syntax (/en/cloud-scale/help/zcql/syntax-exceptions/) - Testing ZCQL v2 Queries (/en/cloud-scale/help/zcql/testing-queries/#using-zcql-v2-in-function-code) -------------------------------------------------------------------------------- {{% divtag class="dF align-center gap-10"%}} # Deprecation of ZCQL API Version v1 {{%/divtag%}} As of **August 2023**, Catalyst has {{%link href="/en/release-notes/all/#2023---august" %}}released{{%/link%}} the **ZCQL API Version** {{%badge%}}v2{{%/badge%}} also known as **ZCQL parser** {{%badge%}}v2{{%/badge%}} and announced the deprecation date of ZCQL API Version {{%badge%}}v1{{%/badge%}} on **February 29, 2024**. <br /> Considering that some of our users have not migrated their codebase from {{%badge%}}v1{{%/badge%}} to {{%badge%}}v2{{%/badge%}}, Catalyst had extended the deprecation date by a month to March 31, 2024. We have now further extended the deprecation. The support for ZCQL parser {{%badge%}}v1{{%/badge%}} will be terminated on **April 30, 2024**. We urge our users to migrate your codebases that employ {{%badge%}}v1{{%/badge%}} to {{%badge%}}v2{{%/badge%}} before this date. To migrate your ZCQL queries to {{%badge%}}v2{{%/badge%}} from {{%badge%}}v1{{%/badge%}}, you need to apply the upgrades syntax to your queries and validate them. To learn about the syntax upgrades and improvements on **ZCQL API Version** {{%badge%}}v2{{%/badge%}}, visit this {{%link href="/en/cloud-scale/help/zcql/syntax-exceptions/" %}}help documentation{{%/link%}}. To learn more about testing {{%badge%}}v2{{%/badge%}} queries in the console, visit this {{%link href="/en/cloud-scale/help/zcql/testing-queries/#using-zcql-v2-in-function-code" %}}help documentation{{%/link%}}. <br /> -------------------------------------------------------------------------------- title: "Changes to Catalyst Authentication" last_updated: "2026-03-18T07:41:08.535Z" source: "https://docs.catalyst.zoho.com/en/announcements/2024/embedded-announcement/" service: "All Services" related: - Catalyst Authentication (/en/cloud-scale/help/authentication/introduction/) - Embedded Authentication (/en/cloud-scale/help/authentication/native-catalyst-authentication/embedded-authentication/introduction/) - Scripts for Embedded Authentication (/en/cloud-scale/help/authentication/native-catalyst-authentication/embedded-authentication/scripts-for-embedded/) - Authentication - Web SDK (/en/sdk/web/v4/cloud-scale/authentication/get-auth-instance/) -------------------------------------------------------------------------------- {{% divtag class="dF align-center gap-10"%}} # Mandatory Notice! Changes to Catalyst Authentication {{%/divtag%}} After continuous and consistent assessments, the Catalyst team has tweaked a few aspects of {{%link href="/en/cloud-scale/help/authentication/introduction/" %}}Authentication{{%/link%}} to make it function better while ensuring easier implementation and enhancing overall application security. ### Changes to Roles Configuration Previously, if you had implemented end-user authentication for your applications with the {{%link href="/en/sdk/web/v4/overview/" %}}Catalyst Web SDK{{%/link%}}, you had the option to configure the {{%link href="/en/cloud-scale/help/authentication/user-management/roles/introduction/" %}}roles{{%/link%}} for each user to be added to, by passing the specific *Role ID*. However, now, any role passed when a user signs up to the app through end-user Authentication implemented via **Web SDK**, will be ignored. When your users sign up to your application, they will be added to the default {{%badge%}}App User{{%/badge%}} role, or to any other default {{%link href="/en/cloud-scale/help/authentication/user-management/roles/implementation/" %}}role that you configure{{%/link%}} in the {{%link href="/en/cloud-scale/help/authentication/user-management/introduction/" %}}User Management{{%/link%}} section. If you specifically require to add users to any other role besides the configured default role, then you can make use of the {{%link href="/en/cloud-scale/help/authentication/whitelisting/custom-user-validation/introduction/" %}}Custom User Validation{{%/link%}} feature. ### Embedded Authentication Enhancements To ensure you continue to utilize and implement the Catalyst {{%link href="/en/cloud-scale/help/authentication/native-catalyst-authentication/embedded-authentication/introduction/" %}}Embedded Authentication{{%/link%}} to its fullest potential, you will need to ensure that you follow and apply the instructions listed here to your Catalyst project. Please read the following pointers carefully and apply them where required: * If you are currently employing any other version of the Catalyst Web SDK to add users to your application using *Embedded Authentication*, you will need to upgrade to **Web SDK v4**, and reconfigure your {{%link href="/en/cloud-scale/help/authentication/native-catalyst-authentication/embedded-authentication/setup-embedded-auth/" %}}embedded authentication setup{{%/link%}} accordingly. * To access the required **Web SDK v4** scripts: - Navigate to the **Authentication** component, present in the *Cloud Scale* service. Click **Set Up** under *Native Catalyst Authentication*. <br /> - Select **Embedded Authentication** and click **Next**. <br /> - Ensure you select **v4** in the **Version** drop-down and copy the required code. <br /> {{%note%}}{{%bold%}}Note:{{%/bold%}} The code snippets are also available in this {{%link href="/en/cloud-scale/help/authentication/native-catalyst-authentication/embedded-authentication/scripts-for-embedded/" %}}help page{{%/link%}}.{{%/note%}} - Upgrading to **Web SDK v4** also allows you to provide our end-users with the options to login to your application using their {{%link href="/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-microsoft-365-social-login" %}}Microsoft 365{{%/link%}}, {{%link href="/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-facebook-social-login" %}}Facebook{{%/link%}}, or {{%link href="/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-linkedin-social-login" %}}LinkedIn{{%/link%}} accounts, including the already existing {{%link href="/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-zoho-social-login" %}}Zoho{{%/link%}} and {{%link href="/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-google-social-login" %}}Google{{%/link%}} social login options. Additionally, the newer version allows you to add users seamlessly with better styling and customization control over your login elements. <br /> * On **March 31st 2025**, all previous versions of the Catalyst Web SDK will cease to function. We strongly urge you to complete the upgrade to **Web SDK v4** and the respective configurations before this deadline. The image below illustrates the new default UI look of the embedded login element. The CSS of this page can be customized using the CSS scripts that can be downloaded from this {{%link href="/en/cloud-scale/help/authentication/native-catalyst-authentication/embedded-authentication/styling-embedded-auth/" %}}help page{{%/link%}}. <br /> If you continue to use any of the older SDK versions beyond the mentioned deadline, then the CSS elements used in the designing of the embedded authentication element will not function as intended, resulting in unintended UI breakage. <br /> * Support to implement *Google social login* has existed since **Web SDK v3**. However, when you upgrade to **Web SDK v4**, you will need to reconfigure the **redirect URLs** accordingly. Steps to configure the *Google social login* can be found {{%link href="/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-google-social-login" %}}here{{%/link%}}. <br /> For more information and help, you can reach out to our support team at {{%link href="mailto:support@zohocatalyst.com" %}}support@zohocatalyst.com{{%/link%}}. Happy Coding! **Team Catalyst** ## 2025 -------------------------------------------------------------------------------- title: "Changes to Mail Component Workflow" last_updated: "2026-03-18T07:41:08.535Z" source: "https://docs.catalyst.zoho.com/en/announcements/2025/mail-changes/" service: "All Services" related: - Catalyst Mail Help Documentation (/en/cloud-scale/help/mail/introduction/) - Verify a Domain (/en/cloud-scale/help/mail/domains/#verify-a-domain) - Verify an Email Address (/en/cloud-scale/help/mail/email-configuration/#verify-an-email-address) -------------------------------------------------------------------------------- {{% divtag class="dF align-center gap-10"%}} # Announcing New Rules of Practice to Implement Catalyst Mail {{%/divtag%}} This announcement is to bring to your attention that with effect from **Feb 1st, 2026**, to send emails using the {{%link href="/en/cloud-scale/help/mail/introduction/" %}}Catalyst Mail{{%/link%}} component the following prerequisites need to be satisfied. 1. You will need to {{%link href="/en/cloud-scale/help/mail/email-configuration/#verify-an-email-address" %}}verify your sender email address{{%/link%}}. 2. You will need to {{%link href="/en/cloud-scale/help/mail/domains/#verify-a-domain" %}}verify your domain{{%/link%}}. This change is being mandated to ensure that the emails sent using the *Mail* component are completely secure. If you attempt to send an email without verifying your domain, an exception will be thrown, and the email will not be sent. -------------------------------------------------------------------------------- title: "Deprecation of Catalyst File Store, Event Listeners, and Cron" last_updated: "2026-03-18T07:41:08.535Z" source: "https://docs.catalyst.zoho.com/en/announcements/2025/fs-el-cron-deprecation-announcement/" service: "All Services" related: - Catalyst Event Listeners (/en/cloud-scale/help/event-listeners/introduction/) - Catalyst File Store (/en/cloud-scale/help/file-store/introduction/) - Catalyst Cron (/en/cloud-scale/help/cron/introduction/) - Catalyst Signals (/en/signals/) - Catalyst Stratus (/en/cloud-scale/help/stratus/introduction/) - Catalyst Job Scheduling (/en/job-scheduling/) -------------------------------------------------------------------------------- {{% divtag class="dF align-center gap-10"%}} # Announcing Deprecation of Catalyst File Store, Event Listeners, and Cron {{%/divtag%}} We would like to announce that the following Catalyst features are now in their deprecation phase and will reach End Of Life (EOL) on **30 April, 2026**- * Catalyst File Store * Catalyst Event Listeners * Catalyst Cron New users who sign up for Catalyst starting today (August 27, 2025) will not be able to view or access these components in their Catalyst projects. For existing Catalyst users, these components will continue to remain operational in their existing projects during the deprecation period until the EOL date mentioned above. You can continue working with your existing resources in the File Store, the events configured in the Event Listeners, and the cron jobs scheduled in Cron in your current Catalyst projects during this period. After the EOL date, these services will not function, and any business logic configured with them will not work. These services will also not be available in any new projects you create. We strongly recommend that you immediately begin planning to migrate your resources, workflows, and business logic configured with these components to the newer, more advanced alternatives listed below. ## Upgrade to Catalyst Stratus from File Store {{%link href="/en/cloud-scale/help/stratus/introduction/" %}}Catalyst Stratus{{%/link%}} is a robust and advanced cloud storage platform that lets you store any type of data as objects in buckets, with unique URLs to reference each object through paths. Stratus provides a host of rich functionalities, including custom object-level permissions, data encryption, versioning, malware scanning, multipart uploads, and more. Stratus is a powerful solution that lets you store anything from basic application files to large videos for streaming platforms. Catalyst enables direct migration of files from the {{%link href="/en/cloud-scale/help/file-store/introduction/" %}}File Store{{%/link%}} to Stratus via the console. All folders and files from your File Store can be migrated into a single bucket in Stratus, with the original directory structure replicated within that bucket. You can migrate files from File Store to Stratus as follows: 1. Access **File Store** from the *CloudScale* service in the Catalyst console for your project. A banner will appear with the migration option. Click **Migrate Now**. <br /> 2. Select the destination bucket in Stratus. If you haven't created a bucket in Stratus yet, create one first and then select it here. Then, click **Next**. <br /> 3. Review the important information shown in the pop-up. Then, type "Filestore Migrate" in the text box and click **Confirm**. <br /> The migration will be scheduled, and you will be notified once it is completed. You can then open **Stratus** from *CloudScale*, and navigate to the selected bucket to access all of your migrated File Store data. Make sure you migrate your data before the EOL date! <br> ## Upgrade to Catalyst Signals from Event Listeners {{%link href="/en/signals/" %}}Catalyst Signals{{%/link%}} is a cutting-edge event bus service that facilitates instant communication between decoupled applications and services. Signals is an advancement from {{%link href="/en/cloud-scale/help/event-listeners/introduction/" %}}Event Listeners{{%/link%}}, offering a rich set of predefined publishers from Zoho services, Catalyst’s own services, as well as third-party services. These publishers come with default events associated with their schemas that you can use instantly, eliminating the need for coding or extensive configurations. With Signals, you can adopt a robust, event-driven architecture to streamline workflows or transfer data with ease. Explore Signals and transfer your existing event-driven architecture from Event Listeners before the EOL date. {{%info%}}Please note that Catalyst does not support direct migration of event-driven logic configured in Event Listeners to Signals.{{%/info%}} <br> ## Upgrade to Catalyst Job Scheduling from Cron {{%link href="/en/job-scheduling/" %}}Catalyst Job Scheduling{{%/link%}} is an advanced job management service that introduces a variety of new components compared to the basic {{%link href="/en/cloud-scale/help/cron/introduction/" %}}CloudScale Cron{{%/link%}}. Job Scheduling provides job pools from where you can create and execute jobs to trigger webhooks, Job functions, Catalyst Circuits, or AppSail services. You can also schedule the submission of jobs with predefined or dynamic crons, and easily track every instance of the job cycle. Job Scheduling gives you greater control over job management, enabling you to handle automated and scheduled workflows seamlessly. Explore Job Scheduling and transfer your existing task schedulers from Cron before the EOL date. {{%info%}}Please note that Catalyst does not provide direct migration of the schedulers configured in Cron to Job Scheduling. {{%/info%}}