How To: Determine and Update the Required .NET / .NET Core Version

Version Affected: All

 

Overview

This article explains which .NET / .NET Core version each SecureAuth Identity Platform release requires, and how to remove an old version left behind after an upgrade. Upgrading the IdP to a new release can require a different .NET or .NET Core version as a prerequisite, and the required version must be adhered to — it cannot be upgraded on its own to a newer one without also upgrading the IdP itself.

Determine and Update the Required .NET / .NET Core Version

1. Find the IdP release in the table below to see which .NET / .NET Core and .NET Framework versions it requires (also available in the SecureAuth Compatibility Guide):

   • Identity Platform 26.0: .NET 8, .NET Framework 4.8 or later.
   • Identity Platform 24.04: .NET 8, .NET Framework 4.8 or later.
   • Identity Platform 23.07: .NET 6, .NET Framework 4.7.2 or later.
   • Identity Platform 22.12: .NET Core 3.1, .NET Framework 4.7.2 or later.
   • Identity Platform 22.02: .NET Core 3.1, .NET Framework 4.7.2 or later.
   • Identity Platform 21.04: .NET Core 2.1, .NET Framework 4.7.2.
   • Identity Platform 20.06: .NET Core 2.1, .NET Framework 4.7.2.
   • Identity Platform 19.07: .NET Core 2.1, .NET Framework 4.7.1.

   For 22.12 and later, SecureAuth Support will work with you on the appropriate .NET updates as part of the upgrade process.

2. During the upgrade, the older .NET / .NET Core version is not removed automatically and can be removed manually afterward. In Add and Remove Programs, identify the entries for the version the new IdP release no longer needs — for example, after an upgrade to 23.07 (which requires .NET 6), the highlighted .NET Core 3.1 entries below are safe to remove:
   
   
    
3. Uninstall the highlighted old-version entries.
4. Run a repair on the current .NET / .NET Core Windows Server Hosting bundle (the one the new IdP release actually requires). This properly updates IIS, since some shared bits were removed in the previous step. Rebooting the server afterward is recommended over just running an IISRESET, to make sure everything picks up correctly.

Special Considerations

If you need a specific .NET / .NET Core version and are running an older IdP release that doesn't support it, you must upgrade the IdP release itself — since the product is built against a specific .NET / .NET Core version, an in-place .NET update alone will not work. Open a ticket with SecureAuth Support to begin the IdP upgrade process.


 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.