Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Users are redirected to SSOCircle or external_logout_complete after cloning or upgrading an instance - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Users are redirected to SSOCircle or external_logout_complete after cloning or upgrading an instance
KB0825390

Users are redirected to SSOCircle or external_logout_complete after cloning or upgrading an instance


6857 Views Last updated : Jun 9, 2023 public Copy Permalink
KB Summary by Now Assist

Issue

After cloning from an instance, users or administrators may be prevented to log in with the error: '‘Username or password not valid’.

Cause

After an upgrade, the latest MultiSSOv2 plugin is enabled, but the correct installation exits are not activated. Test connection may works, but when accessing the instance via browsers, users are redirected to SSOCircle.

Resolution

The system property glide.authenticate.external should be set to false:

/sys_properties_list.do?sysparm_query=name%3Dglide.authenticate.external&sysparm_view=

The Installation Exits with name SAML should be set to false:

/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. The below installation exits and script includes 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. The below installation exits and script includes are set to true:

Plugin

Type

MultiSSOv2

MultiSSOv1

Script Include

MultiSSO_SAML2_Update1

Installation Exit

MultiSSO

MutliSSOLogin

MultiSSOLogout

 

Resetting the MFA on a clone

Use the procedure shown this video to reset the MFA on the cloned instance. 

Related Links

Customization support in MultiSSOv2

How to delete an orphaned Identity Provider record from an instance showing SSO access denied


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.