Search

  • Re: Make the Administration SSL Port Configurable

    I made the changes, and it does work as you intended. It's better than what I had before, but what I really want Websense to do is to make it so that web manager will actually run on port 443 rather than 9443. This just forwards you to port 9443 from the standard ports, which again, is very cool and much appreciated, but hopefully they can just make it run on standard ports to begin with. Thanks, Tommy
    Posted to Websense Web Security (Forum) by Tommy on 9 Mar 2010

  • Re: Make the Administration SSL Port Configurable

    That just means they need to fix the hard coding. :-) It's not important enough to rewrite the product from the ground up. Just seems like a minor oversight. Your initial suggestion is good enough for me.
    Posted to Websense Web Security (Forum) by Tommy on 9 Mar 2010

  • Re: Make the Administration SSL Port Configurable

    Well, I never expected that it was part of the core Websense application, but Apache doesn't configure itself this way inherently. It's as configured by Websense. But, yes, it is awesome. I'll give this a try next week. The case number from Websense support is: 499621
    Posted to Websense Web Security (Forum) by Tommy on 5 Mar 2010

  • Re: Browser Plugin for Troubleshooting

    Proxies can be problematic for some applications, but we'll probably end up going with the content gateway regardless. So that would solve the SSL inspection issue (at a high cost), but it doesn't help with providing better troubleshooting capabilities, or better persistent authentication methods for people like guest users that bring their own equipment, and therefore can't login to the domain or ldap directory. It could be a highly useful enhancement, without or in addition to the content
    Posted to Websense Web Security (Forum) by Tommy on 5 Mar 2010

  • Re: Make the Administration SSL Port Configurable

    Because by default it runs on a non-standard port that web browsers don't use for SSL. Port 443 is for HTTPS by default, and 80 is for HTTP. When you don't use those ports, you have to remember whatever the odd port is and add it onto the end of the URL. In the case of Websense Manager, you chose port 9443 for some reason. Maybe there was a good reason. I just think it's annoying. I have to administer about a hundred products and most of them stick to the standards, but here and there
    Posted to Websense Web Security (Forum) by Tommy on 26 Feb 2010

  • Re: Browser Plugin for Troubleshooting

    Currently, when a user is blocked, they see a Websense block page, which gives them some information, like the user id, category and URL that was blocked. In the case of an SSL encrypted page, they get nothing - just a blank page with a reset connection. Even if they do get the block page, it may be misleading because they were led to that page by an http forward, and they perceive that they're being blocked from www.someplacetheytried.com when they're really being blocked from www.somewheretheywereforwarded
    Posted to Websense Web Security (Forum) by Tommy on 26 Feb 2010

  • Re: Less painful patching

    I'll vote for this as well. Your hot patches are a pain to apply. Spend a little time on your end and save all of your customers a lot of time in the field.
    Posted to Websense Web Security (Forum) by Tommy on 17 Feb 2010

  • Additional Authentication Option

    Hopefully product management has heard this already. I've repeated it many times. When the current transparent authentication models are not available - such as in the case of guest user on our wireless network - the best option that we have to offer them is browser session based authentication from Websense. This is problematic because it's timer based, and just generally unreliable outside of general web browsing. Please develop a client authentication executable or browser plugin that
    Posted to Websense Web Security (Forum) by Tommy on 17 Feb 2010

  • Browser Plugin for Troubleshooting

    Create a web browser plugin that my users can have to gather details about exactly what it is that's not working for them. If a site with embedded content from another site isn't working right, or if it's a mashup site, tracking down exactly what's blocked is a task that the technical folks have to go through, and it's time consuming. You could provide a plugin that traps everything that the user tries to do once enabled, noting what works, what's blocked, and why. It could
    Posted to Websense Web Security (Forum) by Tommy on 17 Feb 2010

  • Make the Administration SSL Port Configurable

    Why does the web manager have to run on port 9443? I worked with support to change the setting to the standard port 443 in six places in your configuration files, which they thought would make it work, but it doesn't. Websense support finally concluded that it's not possible, and it should be submitted as a feature request. Please make it configurable, or at least make it default to the standard port.
    Posted to Websense Web Security (Forum) by Tommy on 17 Feb 2010
Page 1 of 2 (16 items) 1 2 Next > | More Search Options