Force NetSight to use HTTPS
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-02-2015 09:38 AM
Hopefully this is an easy one.....
Is there anyway to force the use of HTTPS directly via the NetSight application. As an example when I delete port 8080 from the 'Web Server' options it forces me to put a port number in, or a simple radio button somewhere that disables it?
Many thanks in advance.
Is there anyway to force the use of HTTPS directly via the NetSight application. As an example when I delete port 8080 from the 'Web Server' options it forces me to put a port number in, or a simple radio button somewhere that disables it?
Many thanks in advance.
14 REPLIES 14
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-18-2016 03:53 PM
Has any progress been made on this issue. I have a customer asking to disable http and would like to be able to give them a timeline if this will be available soon.
Thanks,
Thanks,
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-13-2016 07:45 PM
Managed to workout an option for this.
If you go to your ../NetSight/appdata/ folder and edit the file NSJBoss.properties you can comment out the following line by putting a # in front of it:
enterasys.tomcat.http.port=8080Then the browser is no longer be able to reach NetSight on that port number, thereby forcing the user to use HTTPS.
There might be a way in the same file to redirect anyone trying port 8080 to go to https:8443 instead?
If you go to your ../NetSight/appdata/ folder and edit the file NSJBoss.properties you can comment out the following line by putting a # in front of it:
enterasys.tomcat.http.port=8080Then the browser is no longer be able to reach NetSight on that port number, thereby forcing the user to use HTTPS.
There might be a way in the same file to redirect anyone trying port 8080 to go to https:8443 instead?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-02-2015 01:22 PM
No, there is no way to restrict this via Netsight itself.
If you open a case requesting that as a feature request, we can have it surveyed as a potential feature.
If you open a case requesting that as a feature request, we can have it surveyed as a potential feature.
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-02-2015 12:38 PM
Thanks for posting back.
Apologise if my description my not have been clear.
Just trying to understand your solution, which sounds like to just change the port number for http. This I don't understand, as for example if I changed it to 9090 you would still be able to http in port 9090 instead of 8080, thereby still making it vulnerable.
I was wondering if there is a why in NetSight to disable http (via any port) or redirect all http traffic to https.
Many thanks.
Apologise if my description my not have been clear.
Just trying to understand your solution, which sounds like to just change the port number for http. This I don't understand, as for example if I changed it to 9090 you would still be able to http in port 9090 instead of 8080, thereby still making it vulnerable.
I was wondering if there is a why in NetSight to disable http (via any port) or redirect all http traffic to https.
Many thanks.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-02-2015 12:25 PM
You can change the ports using Tools->Options->Web Server
For certain you want to do this only on Netsight Server appliances only, that don't use other ports for the proposed ones.
So this means not using in with Netsight Server than runs on the Windows Server Platform, where we have seen interference issues.
Be sure to test it, before assuming it will work in full deployment for your sight.
For certain you want to do this only on Netsight Server appliances only, that don't use other ports for the proposed ones.
So this means not using in with Netsight Server than runs on the Windows Server Platform, where we have seen interference issues.
Be sure to test it, before assuming it will work in full deployment for your sight.
