Login Redirect Issues

[nluoma]

We have been using ServiceNow for several years (started on Berlin) and have been using a customized version of the original ess portal up until our upgrade to Yokohama last month and are now moving to the Service Portal (/sp). This means that the non-ITIL users now need to go to a new URL.

We have updated all desktop shortcuts to point to the new /sp site, but after years of using /ess there are saved shortcuts that are still being used. (We have sent out emails telling everyone about the URL change, but users don't always read emails, and often don't realize how shortcuts and bookmarks work.)

I followed the instructions to set up the automatic routing using the SPEntryPage and the different sys properties.  But, the issue is that some users are coming in with an incorrect redirect url. I cannot set it up so ITIL users go to the main interface while all others go to /sp because we have different portals available for some groups (for example, our Kiosk users and our Retail Stores) and cannot ignore a direct request. 

I have added a redirect script to the /ess page, which works for users who are already logged in. The process still sends them to the /ess page, but it then passes them on to the /sp page. (I did remove most of the content on the old /ess page to make this faster.)

However, if a non-ITIL user who is not logged in tries to go to /ess (by using a shortcut or bookmark, for example), the system prompts them to log in and then redirects them to /ess.do which gives them a 404 error. This is not a good result for end users, obviously, so I want get them logged in and going to /sp.

I've looked at the SPEntryPage script, and I'm sure there has to be some way to modify this so that we can redirect only the /ess requests, while still honoring the other portals, but I haven't been able to figure out how to do this.

Does anyone have an idea how I would address this? I've scoured the forums, but can't find anything that applies. There appear to be several approaches if you are moving between the newer Service Portals, but very little on what to do with the old content management portals.

[nluoma]

I have followed the steps in the articles recommended, created the necessary sys properties for the first pages, defined a default service portal, and so on. Which works as long as the user isn't using a link to the old ess site.

What appears to be the main problem is that the log in script (wherever it is) is changing the redirect URL to ess.do. So logged in users are going to /ess and non-logged in users are going to /ess.do. I can address one or the other of these by adjusting the content site, but not both. I have tried:

- Adding a redirect script onto the home page of the ess portal (url suffix: ess). This works for logged in users, but not non-logged in users.

- Changed the url suffix for the ess portal to ess.do. This works for non-logged in users, but not logged in users.

- Make the ess portal not active. This gives everyone a 404 error if they try to go to that page.

I am not sure where the log in redirect script is, so I can't see why it's tacking on the ".do".