side_door is not working

[Prashant Rakesh]

Hi,

I have configured Multi SSO and forced login method to use external authentication. The issue is now this side_door.do page is not working. I need to get this working for few days and then we can disable this option. Does anyone faced the same issue? Please suggest.

[amolrajurkar]

I think you have to logout from login.do and then try side_door.do. It will show you a login screen then.

[cyrus1]

can non admin users also login through /login.do if they have local account ?

[Prashant Rakesh]

Yes, they can, if they have stored password in servicenow.

Regards,

Prashant Rakesh

[cyrus1]

We have created local account and set password also but still not able to login through /login.do. What preventing it from login?

[Prashant Rakesh]

@Nishant007

Can you post a screenshot of the error you are getting?

There are 2 ways of fixing the issue. You'll need a directly LDAP integration (or store passwords in servicenow) I believe this will help you for the Multi Logins.

Deploying multiple provider single sign-on, available since Eureka will allow local authentication.

Multiple Provider Single Sign-On - ServiceNow Wiki<https://community.servicenow.com/external-link.jspa?url=http%3A//wiki.servicenow.com/index.php%3Ftitle%3DMultiple_Provider_Single_Sign-On%23Configuring_Multi-Provider_SSO_Properties%26gsc.tab%3D0>

1 Overview

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. The integration supports any combination of local and external authentication methods on a single instance:

· SAML 2.0

· Digest Authentication

· LDAP

· Local database authentication

For example, a globally dispersed corporation might require one SSO provider for their employees, a different one for their vendors, and local database authentication for their administrators. Alternatively, a company might implement SAML 2.0<https://community.servicenow.com/external-link.jspa?url=http%3A//wiki.servicenow.com/index.php%3Ftitle%3DSAML_2.0_Web_Browser_SSO_Profile> and a digest token<https://community.servicenow.com/external-link.jspa?url=http%3A//wiki.servicenow.com/index.php%3Ftitle%3DDigest_Token_Authentication>authentication solutions on the same instance.

This feature is available starting with the Eureka release<https://community.servicenow.com/external-link.jspa?url=http%3A//wiki.servicenow.com/index.php%3Ftitle%3DEureka_Release_Notes>.

However using side_door.do will also allow access to the instance without using SSO

External Authentication (Single Sign-On - SSO) - ServiceNow Wiki<https://community.servicenow.com/external-link.jspa?url=http%3A//wiki.servicenow.com/%3Ftitle%3DExternal_Authentication_%2528Single_Sign-On_-_SSO%2529%23Bypassing_External_Authentication>

..

3.1 Bypassing External Authentication

Administrators may need to bypass external authentication when testing an SSO integration. Administrators can use the following URL to bypass external authentication and log in with a local ServiceNow user. Note that a logged-in user cannot access this page. Attempting to access this page while logged in produces a page not found error.

http://<your-instance>.service-now.com/side_door.do

<https://community.servicenow.com/external-link.jspa?url=http%3A//wiki.servicenow.com/index.php%3Ftitle%3DFile%3AWarning.gif>

Note: You can still log in as an inactive user if the user is not locked out. See Making a User Inactive<https://community.servicenow.com/external-link.jspa?url=http%3A//wiki.servicenow.com/index.php%3Ftitle%3DManaging_User_Sessions%23Marking_a_User_Inactive> for more information.

Regards,

Prashant Rakesh