Version Affected: 19.07.01+
Description:
In order to meet certain requirements, it may be necessary to upgrade the .NET Core and .NET Framework versions on the SecureAuth appliances.
The minimum supported versions can be found here.
|
Product release |
.NET and .NET Core version |
.NET Framework version |
Note |
|---|---|---|---|
|
Identity Platform 24.04 |
.NET 8 |
4.8 or later |
Identity Platform 24.04 release requires .NET 8. SecureAuth Support will work with you on the appropriate updates as part of the upgrade process. |
|
Identity Platform 23.07 |
.NET 6 |
4.7.2 or later |
Identity Platform 23.07 release requires .NET 6. SecureAuth Support will work with you on the appropriate updates as part of the upgrade process. |
|
Identity Platform 22.12 |
.NET Core 3.1 |
4.7.2 or later |
Identity Platform 22.12 release requires .NET Core 3.1. SecureAuth Support will work with you on the appropriate updates as part of the upgrade process. |
|
Identity Platform 22.02 |
.NET Core 3.1 |
4.7.2 or later |
Upgrades to the Identity Platform 22.02 release requires .NET Core 3.1. SecureAuth Support will work with you on the appropriate updates as part of the upgrade process. |
|
Identity Platform 21.04 |
.NET Core 2.1 |
4.7.2 |
|
|
Identity Platform 20.06 |
.NET Core 2.1 |
4.7.2 |
|
|
Identity Platform 19.07 |
.NET Core 2.1 |
4.7.1 |
Special Considerations:
Note that if you need a specific version of .NET Core, such as 3.1 in an instance where you are running Identity Platform 21.04 or below, you must upgrade the Identity Platform version in order to be in .NET Core 3.1. Since the product is built upon a specific .NET Core version, an in-place upgrade will not work. Please raise a ticket on the SecureAuth Support page in order to begin the upgrade process with a Support Engineer.
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.
Comments
Please sign in to leave a comment.