Skip to main content

LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

FAQ: Using Transparent Authentication Mechanism with FireFox

Expand / Collapse


  • Question
    As a result of the new Transparent Authentication mechanism added in Vital Security software version 8.4.3, the browser allows the end-user to connect to the internet without sending requests for authentication from the end-user.

    This authentication request arrives from the browser as a result of the HTTP 401 Unauthorized Response sent from the web-server.

    If the authentication domain is resolvable as a hostname inside the orginization, the IE browser will forward authentication details automatically.
    However, the FireFox browser will not do it automatically.

    How can we enable this automatic option  for FireFox  so that it does not send repeated requests for authentication to the end-user?

  • Answer
    In order to enable this automatic option for the FireFox browser, please do the following:
    1. Open FireFox browser.
    2. Type about:config in the FireFox address bar.
    3. Select network.automatic-ntlm-auth.trusted-uris in the Filter bar.
    4. Type in the virtual redirection hostname that you have defined for your Finjan appliance (e.g. vhost in the example below):

    5. Virtual Redirection Hostname must be defined exactly as it is set for Finjan appliance:


  • VSOS
    8.4.3

  • This article applies to:
    NG 1000
    NG 5000
    NG 8000
    This article was previously published as:
    Finjan KB 1390

    To contact LevelBlue about this article or to request support:


    Rate this Article:
         

    Add Your Comments


    Comment submission is disabled for anonymous users.
    Please send feedback to Trustwave Technical Support or the Webmaster
    .