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.
User gets logged out immediately after logging in - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • User gets logged out immediately after logging in
KB0778207

User gets logged out immediately after logging in


15295 Views Last updated : Apr 26, 2024 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

The multiple provider single sign-on feature allows organizations to use several SSO identity providers (IdPs) to manage authentication as well as retain local database (basic) authentication.

 

Installation exits are customizations that exit from Java to call a script before returning to Java. They are usually related to login, logout, validate password and external authentication. The installation exits are located on System Definition > Installation Exits. Some installation exits can be overridden with a custom script that replaces the one in the default installation exit.

 

Each SSO plugin comes with its installation exits.

When the  Multi-SSO plugin is installed it comes with its installation exits, the previous SAML installation exits are no longer required and the system will make them inactive.

 

 

 

Release

Helsinki and later

Cause

After enabling Multi-SSO, some SSO validations may fail if the Multi-SSO installation scripts do not execute first.

There are some exceptional cases where some SAML* installation exits remain active (incorrectly) after the Multi-SSO plugin is installed.

e.g. If SAML is already active at the time you activated Multiple Single Sign-On and if you already customized the SAML installation exits.

 

This could cause the logs will show the following errors:

WARNING *** WARNING *** Evaluator: org.mozilla.javascript.EcmaError: Cannot convert null to an object.

Caused by error in Script Include: 'SAML2_update1' at line 35

 

32: this.lastGeneratedRequestID = null;

33: this.inResponseTo = null;

34: this.logoutFailureEventId = "saml2.logout.validation.failed";

==> 35: this.certGR = this.getCertGR();

36:

37: // Keep SAMLAssertion object for validation

38: this.SAMLResponseObject = null;

Resolution

To resolve the problem, if Multi-SSO is installed correctly, validate the following installation exits have Active set to False:

Installation exit

 

Active

SAML2Logout

=

false

SAML2Logout_update1

=

false

SAML2SingleSignon

=

false

SAML2SingleSignon_update1

=

false

MultiSSO

=

true

MultiSSOLogin

=

true

MultiSSOLogout

=

true

 

Here is the result:

 


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.