Disabling side_door.doIssue The side_door.do page enables access to an instance in the event that there is an issue with SSO (Single Sign On). Although it is possible to disable this, we recommend leaving it intact and running the Restricting local login script in the following document, which sets the passwords of all users to a random number so they cannot log in. This still gives you the ability to have a local admin account for use in case of an SSO (Single Sign On) failure, while stopping your other users from accessing the instance by any means other than SSO(Single Sign On).ResolutionForce single sign-on login (SSO) only Additionally, you can rename the side_door.do page to something else that is less obvious or well known. To do this follow these steps: Create a new property on the sys_properties table named glide.authenticate.external.side_door_uri, of a type String, and a value of whatever you would like the page to be named (such as "side_door")Flush the cache. (You can enter cache.do in the Application Navigator field. Doing so on a Production instance may temporarily impact performance as the caches are rebuilt.)To test, log out of your instance, and enter in the following URL: https://[instance name].service-now.com/[value of property].do However, if you still need to disable side_door.do, you can so by leaving the value for the glide.authenticate.external.side_door_uri system property blank. As mentioned above, using this property is not supported by ServiceNow technical support, and we strongly recommend that you have a way to access your instance using the side door method, in case your external authentication fails or is not able to authenticate users. Since disabling side_door is a last resort, please perform sufficient testing before making the change.