How to manually upgrade MultiSSO V2 for customized CSE instances<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Upgrade a customized CSE instance to MultiSSO V2 while preserving your MultiSSO customizations and existing SAML flows. MultiSSO V2 updates its internal OpenSAML library from version 2.4.1 to version 3.4.1 to address known vulnerabilities. The update changes existing script includes, installation exits, and other MultiSSO components. When you upgrade to a release that includes MultiSSO V2, your instance receives the updated version. If your instance is on a release before the New York release and contains customized MultiSSO resources, use the manual upgrade path in this article. This process preserves your customizations and allows your existing SAML flows to continue working without changes. To determine whether your instance uses MultiSSO V2, check the glide.authenticate.multissov2_feature.enabled system property. Your instance does not use MultiSSO V2 when either of the following conditions applies: The glide.authenticate.multissov2_feature.enabled system property does not exist.The property value is set to false. Review the OOB available customization samples before you apply a solution to your instance. Customized instances A customized instance contains changes to one or more MultiSSO resources. To upgrade a customized instance to MultiSSO V2, complete the manual upgrade instructions in this KB Article. Contact Now Support if your customizations prevent you from completing the upgrade. Upgrade path for customized instances To review the customization audit results, go to SAML Lib Upgrade Customization Audit Results in the Platform Security instance.In the Instance Name column, search for your instance.Open the instance record.Review the Analysis and Solution Categories columns.If the Solution Categories column does not contain a mapped solution, complete any applicable instructions in the Analysis column. Then, complete the Steps to Upgrade to MultiSSO V2 section.If the Analysis column requires changes or the Solution Categories column contains one or more mapped solutions, note each listed solution category.To locate a mapped solution, go to MultiSSO Customization Solutions in the Platform Security instance, and search for the solution category.Open the customization solution category.In the Request and Response solution for V2 column, locate the code changes for your instance. Search for the instance name when the list contains many entries.Apply the code changes to your instance as instructed at the beginning of the solution category.Complete the Steps to Upgrade to MultiSSO V2 section. Steps to upgrade to MultiSSO V2 To check the MultiSSO V2 feature setting, search for the glide.authenticate.multissov2_feature.enabled system property.If the property exists and its value is false, set the value to true.If the property does not exist, create a system property with the following values: Name: glide.authenticate.multissov2_feature.enabledType: true or falseValue: true To refresh the Multiple Provider SSO configuration, go to the Multiple Provider SSO Properties page.Clear the Enable multiple provider SSO check box, and save the setting.Select the Enable multiple provider SSO check box, and save the setting. MultiSSO V2 is now enabled, and the V2 installation exits are active. To validate the upgrade, go to your identity provider record, and select Test Connection.Confirm that the connection test succeeds. A successful test confirms that the upgrade is complete.