Redirecting to service-now.com

[hafka]

It seems that we cannot redirect to Service-now.com using domain name something like this: service-now.ourdomain.com.
Can I found somewhere in the documentation that this feature is disabled or should it be possible?

[Oliver D_sereck]

Hi Hafka,

We did it like this:

Created a new subdomain, for example: snc.ourdomain.com
Created an index.html file with the following content:

CONTENT="0; URL=https://YOURINSTANCE.service-now.com">
Upload via FTP to our Hoster/Server under your new Subdomain.
When going to your subdomain, you are automatically redirected after 0 seconds to your instance.

I did this for our PROD and DEV instances.

Cheers,
OD

[aaron_burruss]

The ServiceNow load balancer infrastructure is looking for the HTTP_HOST header in the inbound request, and attempting to match . Once matched, it knows which application server to send the request to. This means that if the inbound request is .yourdomain.com, our load balancers won't know what to do with it. Using a DNS CNAME (or something similar) to redirect your internal hostname to the ServiceNow hostname isn't sufficient.

The above suggestion by od will allow you to present your users with an internal URL for their bookmarks, etc, and will then redirect to yourinstance.service-now.com (ie: the URL in the address bar of the user's browser will change). Alternatively, you can set up a similar subdomain, configure that site on your network to act as a reverse proxy. This would allow the end user's bookmark, documentation, etc to all reflect your "internal" URL/branding, and also would keep the user's address bar in their browser to retain the "internal" URL throughout their session.

Hope this helps!

[geoffcox]

With that design, aren't you going to throw away anything else in the URL? What if someone is trying to query a table, for example?

[aaron_burruss]

geoffcox, you're referring to od's proposed solution, correct?

I believe you are correct. That "Redirect" configuration is going to take whatever request comes in for whatever.mydomain.com (and any subsequent URI) and change it to instance.service-now.com.

If the reverse proxy mechanism I described is implemented properly, then it will take any of the URI and append onto the request that gets sent into ServiceNow. Here's an example of how you'd do it in apache:

With mod_rewrite:
RewriteCond %{HTTP_HOST} ^helpdesk.yourdomain.com$ [NC]
RewriteRule ^/(.*)$ https://yourinstance.service-now.com/$1 [P,L]

Or with using mod_proxy within the helpdesk.yourdomain.com virtual host:


ProxyRequests off
ProxyPass / https://yourinstance.service-now.com/
ProxyPassReverse / https://yourinstance.service-now.com/


There are other ways to accomplish this using solutions other than Apache (ie: network appliance such as an F5), but the concept is the same.