Multi-Provider SSO IdP profile can not be activated in an instanceDescriptionWhen a user sets up an Identity-Provider profile after enabling Multi-Provider SSO plugin on the instance, ServiceNow recommends users test the IdP connection before activating the external authentication on the instance. If the user has not completed the IdP configuration then the Active checkbox is grayed out by default and the user can not activate the IdP profile. Please check the below screenshot. Release or EnvironmentStarting from the Jakarta release.CauseThe reason is from Jakarta's release, ServiceNow introduces a new system property named "glide.authenticate.multisso.test.connection.mandatory". However, this property does not exist in the OOB instance. Enabling this property the system will force to test connection for the IdP profile before activation. In the Activate UI action script as below, it will check the property value to decide whether to activate the IdP profile record. Below if condition will check the property value and if the property value is true then the system will force to test the IdP connection and take actions accordingly based on the test result. If the property value is false then the system will bypass the condition check and enable active UI action for users. Regardless of the value, the property must be on the instance to pass the condition check in the UI action script. if(GlideProperties.getBoolean("glide.authenticate.multisso.test.connection.mandatory", true))ResolutionManually create the below system property in the sys_properties.list table on the instance. Set the value to false so it will not be mandatory to test the IdP connections. Name: glide.authenticate.multisso.test.connection.mandatory Type: true | false Value: false