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.
If you want to disable local login entirely (only if you are implementing SSO), the first option you should consider is to set the ‘glide.authentication.external.disable_local_login’ redirection property. This property was introduced in the Fall 2009 Stable 2 build so you may have to upgrade to get it. It allows you to disable login on the standard welcome page unless SSO credentials were present. It needs to be used along with a second redirect property that will redirect non-sso users to the page of your choice. These properties are documented here…
Another option you might try is to install the content management plugin and configure a custom welcome page. This option could be used to customize the login page and present whatever information you wanted to show. You could use this with SSO or if you just wanted to customize the look and feel of your Service-now login page.
When you install the content management plugin, you’ll have a module in your instance called ‘Configuration Page’. You can specify the login page for your instance in the ‘Login page’ field on the configuration page. Then when anyone came to your instance they would see the page specified (which could be any html page you want to create).
In a shared instance scenario, is it possible to display a custom login page based on the url?
servicedesk.company1.ca >> custom login page 1
servicedesk.company2.ca >> custom login page 2
servicedesk.company3.ca >> custom login page 3
This is possible with the Content Management System in ServiceNow. You would have to set up separate login pages in your CMS for each company and then use the page suffix as the pointer to the different login pages. You shouldn’t even have to set up a full CMS site to do this. Your URLs would look something like this…
Something that won’t be so easy to separate is the page that users end up on when they log out of the system. Typically users are brought back to the standard login page and I don’t know of a simple way to get them back to the same company-specific page they hit when they came in. You’d probably just have to make your standard login page look as generic as possible. I’m not sure what challenges you might face with this but it looks like it would work.
Is it possible to edit the login block (shown in the inset picture above)? I’m using global client script to manipulate the DOM in order to change “Login” to “Legacy Login”, but the screen has to render before I can execute the script so it looks a little sloppy when the page first loads, and the script interrupts your typing when you’re trying to log in.
Only simple way I can think of is to try and see if you can adjust a UI message record.