erviceNow makes configuring SSO into your ServiceNow instance very simple. By enabling a plugin and configuring a couple of properties, single sign-on can be set up in less than 10 minutes. Documentation surrounding these SSO methods are also well done and easy to follow.
Recently, I’ve come across a number or clients that want to use ServiceNow as their main company portal and wish to configure their ServiceNow instance to generate an SSO token that can be consumed by a third party service provider. In other words, they desire to have outbound single sign-on directed to of their other internal applications. Because of this increasingly common request, I have created an update set that can be used for such a purpose called, Outbound Single Sign-on via Digested Token.
or some ServiceNow implementations, there may be a need to modify the default login page. In other implementations, it may be necessary or desirable to remove the login page altogether (this scenario would only apply if you have set up Single sign-on for your instance and you didn’t want users to authenticate directly against Service-now). Even if you thought you wanted to disable the login page entirely I wouldn’t recommend it unless you had some very stringent security requirements that you couldn’t make an exception to. The problem with removing the page entirely is that you cut off access to your ServiceNow instance entirely if your SSO portal goes down. In an event like this, you probably want your ServiceNow administrator – and potentially process users – to be able to access the instance through a local login account (which requires a login page!).
Whatever the reason is, you may find it necessary to modify the behavior of the ServiceNow login page. If you do, there are a couple of options I would recommend.