Skip to main content

CXO Identity Provider Change Log

This page contains a change log of CXO’s Identity Provider as a curated, chronologically ordered list of notable changes for each version. The format is based on Keep a Changelog.

Note: While following numbering syntax, the release versioning does not adhere to Semantic Versioning rules.

For more information, see Installation and Enabling CXO Identity Provider.

25.3.0

Date: November 24, 2025

Changed

  • Updated the license.

  • Upgraded NuGet packages.

24.3.0

Date: December 18, 2024

Changed

24.2.0

Date: August 13, 2024

Changed

  • Update Duende identityserver to prevent open redirects

    • More information at Duende Software Blog

23.3.1

Date: 20-11-2023

Fixed

  • Auto generated certificate didn’t work (DEV-29258)

23.3.0

Date: 10-10-2023

Fixed

  • Configure Duende License for IDP (DEV-28713)

Important: From this version onwards cross-server communication to IDP must go over HTTPS.

1.0.23087.01

Date: 29-03-2023

Fixed

  • Updated React in IDP to Active supported version (18.x). (DEV-27122)

1.0.21327.01

Date: 23-11-2021

Fixed

  • CXO Identity Provider does not work for new when only .net core 3.1 is installed. (DEV-25886)

  • New generic clients created in CXO Identity Provider do not work (DEV-25889)

1.0.21322.04 (Warning!!! Please read notes before installation)

Date: 19-11-2021

Upgrade instructions:

  • Install ASP.NET Core Runtime 3.1 Hosting Bundle (Download .NET Core 3.1 (Linux, macOS, and Windows) (microsoft.com))

  • Restart the server

  • Create backup of master database prior to installation of CXO Identity Provider

  • Install new version of CXO Identity Provider

  • If you use any OneStream or User Synchronization client types, then recreate secrets for all your clients and replace private-key in your OneStream Business Rule or PowerShell scripts used for user synchronization.

Important:

  • The new version contains significant changes in the database structure. It is highly recommended creating a backup of cxo master database before installation. The database migration is performed during start-up of CXO Identity Provider application.

  • Older version of CXO Identity Provider did not check validity of the certificates used for OneStream or UserSynchronization clients. The OneStream and UserSynchronization clients created by previous versions have validity of 2 years. In the new version, this has been changed to 100 years. Even if the certificates for your OneStream or UserSynchronization clients have not expired yet, it is still highly recommended recreating secrets for all OneStream or UserSynchronization clients after installation of CXO Identity Provider to avoid any issues in the near future.

Added

  • Migration from unsupported .NET Core 2.0 version to .NET Core 3.1

  • Check on validity of the certificates used by OneStream and UserSynchronization clients. (Breaking change: See note above for more details)

  • Extend validity of the certificates used by new OneStream and UserSynchronization clients from 2 years to 100 years.

Was this article helpful?

We're sorry to hear that.