Upgrade Considerations for CSM 10.2.0

Find important information to help plan your upgrade to the latest version of CSM.

Installation Requirements for .NET Framework

Microsoft .NET Framework 4.8 must be installed on all server and client machines prior to upgrading CSM 10.2.0. During the CSM upgrade process, the Auto-Deploy feature performs a check to confirm that .NET Framework 4.8 is installed on the machine. If the 4.8 version of .NET Framework is not detected, the Auto-Deploy feature installs it before continuing to upgrade CSM 10.2.0.

Custom Language Packs

Platform strings for custom language packs are not updated as part of the upgrade process. After the base platform strings are updated, update any custom language packs you have installed to include the new strings in custom languages.

For information on updating the language packs, see https://zero.comaround.com/link/ffd56b309a394ea07de908d8762fdf1d/.

Unified SAML Authentication through Cherwell REST API

Note: The information in this section applies to upgrades from earlier than CSM 10.0.0. If you are upgrading to this release from CSM 10.0.0, you can ignore this information.

Starting with CSM 10.0.0, SAML authentication flows through a single endpoint on the Cherwell REST API, no longer through the Cherwell Web Service. This change in endpoint is part of an effort to unify the authentication process of Cherwell applications and services through the Cherwell REST API, simplifying configuration, maintenance, and troubleshooting.

Due to this change in authentication, if SAML is already configured and enabled in your environment, you are presented with the SAML login window during upgrade; however, that login window will display a server error by default. To move forward with the upgrade, either cancel or close the SAML login window and then log in with your internal CSM credentials.

To resolve the server error on the SAML login window after upgrade, the SAML endpoint must be updated in both CSM and the SAML Service Provider.

Update CSM with SAML Endpoint

To assist with the CSM update, the existing SAML web service URL is automatically updated to match the Cherwell REST API URL in the upgrade prompt. For example, if the REST API URL is https://host.domain/CherwellAPI/api/, the SAML web service URL will be updated to https://host.domain/CherwellAPI (without the /api at the end of the path).

If you cancel the prompt for the REST API URL during upgrade, and then later set the URL either in the Security section of CSM Administrator or through the command line, you must manually configure the SAML Service Provider web service URL in the SAML Settings window in CSM Administrator in the following format: https://host.domain/CherwellAPI. For more information, see Configure SAML as a CSM Service Provider.

Update SAML Service Provider Assertion Endpoint

After the SAML Service Provider web service URL is updated in CSM, the SAML assertion endpoint must be updated in your SAML Service Provider. The endpoint is the URL to the Cherwell web service page that is used as the assertion consumer. This URL is the domain followed by CherwellAPI/saml/assertion. For example, if the previous URL is https://www.mycompany.com/CherwellService/saml/assertion.aspx, the new URL should be changed to https://www.mycompany.com/CherwellAPI/saml/assertion.
Note: The Cherwell REST API endpoint is the only required endpoint. If the Cherwell Web Service endpoint still exists, simply delete it, as it is no longer supported. Also, file extensions such as .cshtml are no longer valid.

For more information, see Manually Add CSM as a Relying Party.

Upgrade Considerations for Earlier Versions