Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

Configuration required on self hosted SN APP server to allow HTTPS

bkw
Kilo Explorer

This is for an  interface with SNOW appliance which uses HTTPS only.  SN instance is  self hosted Eureka instance on Redhat. SNOW interface section has been deployed, just require details on how to configure the SN APP server to use HTTPS. Currently user access is on HTTP.  Previously tried configuring glide.properties but no joy with HTTPS access.

9 REPLIES 9

Can you try restarting the ServiceNow node and then run this instead:


netstat -nlp | grep 8443


Hi Tim,


i ran the command ,but no output. any more ideas?


[root@eecsaruh2hor285 ~]# netstat -nlp |grep 8443


[root@eecsaruh2hor285 ~]#


This is difficult to debug through this forum, are you able to open an incident in HI for this instance? Then the relevant Customer Support team would be able to run a Webex with you and help with the setup.


swong212
Kilo Contributor

I went through the same thought process...



In the end, your SSL termination point should be at the load balancer.   Not the application server(s).



That way you can examine headers and reverse proxy etc.



Suggest you go with that.


jeffreyluto
Tera Contributor

The "02-https.properties" file under the conf/overrides.d directory that is required when you do conversion of Keystore to BCKS and KMF?  Our DEV works without it because it's HTTP and no load balancer. But my QA and Prod have load balancers.  So creating this file from scratch like as follows? or similar is required? 

tomcat.connector.main.redirectPort=8443

 

tomcat.connector.secure.port=8443

 

tomcat.connector.secure.scheme=https

 

tomcat.connector.secure.secure=true

 

tomcat.connector.secure.SSLEnabled=true

 

tomcat.connector.secure.clientAuth=false

 

tomcat.connector.secure.sslProtocol=TLS

 

tomcat.connector.secure.keystoreFile=../conf/<instance>.keystore

 

tomcat.connector.secure.keystorePass=<password>