Official Way for Our own domain redirect to ServiceNow instance

[marcolee]

I would like to know more about Web or Proxy architecture on this case. Please kindly explain more.

ServiceNow does not provide or support this facility. In order to accomplish this, you must procure and configure a web or proxy architecture to answer the requests for https://support.<mydomain>.com and proxy those requests to the URL provided by ServiceNow (https://<instance>.service-now.com).

[Goran WitchDoc]

Hi,

I had this question up when I worked at my last employee.

Im not sure what youre requirements are, but I hope this will give you an overview.

First of all. ServiceNow doesn't have the functionality that some other cloud companies has which pretty much handles the domain redirecting etc.

For example:

you want support.acme.com to go to your acmeprod.service-now.com. Now, you can't do this redirect in dns since the the name support.acme.com needs to point to a ip-adress and not another name. Problem here is that   your instance doesn't have a own unique IP-adress meaning that when the browser doesn't know where to go when it hits that ip-adress and ServiceNows servers doesn't point to the right instance. Now this is the functionality that some other cloud companies has and I hope ServiceNow might do that in the future, since it would been a great help. Especially since all other options require infrastructure at your end and that was what you where hoping not needing when going into the cloud. And this might even be a Single Point of Failure (SPOF) to reach the instance if it goes down.

Now, you pretty much have 2 alternative.

1. You want the user to type in support.acme.com and then in the browser it will change to acmeprod.service-now.com and shows the login page/portal what you want to be. This is done by having a proxy server at your end and you point support.acme.com to that server and it will   then redirect you to the instance and that when the URL changes in the browser. after this first connection. All traffic is directly between end user and instance

2. You never want the user to see acmeprod.service-now.com and always see support.acme.com. Then you need the above solution and a reverse proxy. This will give the result you want, but it will also make all traffic go through the proxy. which can be big och little load, depending one the size of company/users etc.

What to remember as well is that both options makes the proxy a SPOF. If the proxy server isn't available, support.acme.com doesn't work.

I hope this answers your questions.

//Göran

[rewanthrr]

Hi Göran,

We have similar requirement. Could you please help me with the detailed steps on the 1st option.

Appreciate you help!

Thanks,

RRR  

[Goran WitchDoc]

Hi,

You actually don't need step 1 anymore. Since a lot has changed with ServiceNow since I posted this. Nowdays you can actually setup a custom URL for your instance. You can read more about it here: https://docs.servicenow.com/bundle/orlando-platform-administration/page/integrate/authentication/tas.... Just let me know if you have any other questions.

//Göran
Feel free to connect:
LinkedIn
Subscribe to my YouTube Channel
or look at my Book: The Witch Doctor’s Guide To ServiceNow