618 views

Description

Users are redirected to SSOCircle after cloning or upgrading to NewYork or Orlando 

Cause

After upgrade the latest MultiSSOv2 plugin is enabled and the correct installation exits is not activated.

NOTE : Test connection works , but when accessing the instance via browsers users are redirected to SSOCircle

Resolution

For both UserCase1 and UseCase2

1.glide.authenticate.external is set to false

(https://instancename.service-now.com/sys_properties_list.do?sysparm_query=name%3Dglide.authenticate.external&sysparm_view=)

2. Installation exits with name SAML is set to false

(https://instancename.service-now.com/sys_installation_exit_list.do?sysparm_query=nameSTARTSWITHSAML&sysparm_view=)


UseCase 1 :

1. glide.authenticate.multissov2_feature.enabled = true

2. In the Identity Provider record , Go to Advance Tab --> Single Sign On Script : MultiSSOv2_SAML2_custom

3. Following installation exits and Script include are set to true.

Plugin

Type

MultiSSOv2

MultiSSOv2

Script Include

MultiSSOv2_SAML2_custom

Installation Exit

MultiSSOv2

MutliSSOLogin

MultiSSOLogoutv2




UseCase 2:

1. glide.authenticate.multissov2_feature.enabled = false OR this property is not defined in the sys_properties.list table

2. In the Identity Provider record , Go to Advance Tab --> Single Sign On Script : MultiSSO_SAML2_Update1

3. Following installation exits and Script include are set to true.

Plugin

Type

MultiSSOv2

MultiSSOv2

Script Include

MultiSSO_SAML2_Update1

Installation Exit

MultiSSO

MutliSSOLogin

MultiSSOLogout

Additional Information

Users are redirected to SSOCircle after cloning or upgrading to NewYork or Orlando

Article Information

Last Updated:2020-06-15 11:04:49
Published:2020-06-15