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
View All Services
Solutions
BY INDUSTRY
BY REGULATION
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
We reduce cyber risk and fortify organizations
Awards and Accolades
Recognition by analysts and media outlets
LevelBlue SpiderLabs
Global researchers, ethical hackers, and responders
LevelBlue Security Operations Platforms
Unprecedented security visibility and control
Security Colony
Access to cybersecurity threat protection resources
Partners
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Register
Login
Resources
BLOGS
UPCOMING
MEDIA & ASSETS
NOTICES
HELP
Loading...
Loading...

LevelBlue Knowledge Base

Home » Knowledgebase » Legacy Products » Secure Web Gateway » INFO: How To Exclude Web Applications From the Authentication...

INFO: How To Exclude Web Applications From the Authentication Mechanism

Expand / Collapse
Show/Hide Article Tools


  • Description
    Some web applications (such as Citrix Webmeeting) get stuck due to authentication requests which can not be handled by such applications.
    This article describes how to exclude them from authentication mechanism.

  • Symptoms
    Example:
    Citrix Webmeeting gets stuck, or the connection setup wizard does not succeed.

  • Cause
    An authentication request is sent to the client in a later session stage, but the application cannot handle it correctly.

  • Solution
    The solution is to exclude this application / site from authentication mechanism.

    Drawback: The client is not authenticated or identified anymore and the policy for unknown users is applied.

    1. Step: Create a list of URLs you want to exclude (It might be necessary to do a packet trace and analyze the destination URLs)



    2. Step: add a condition to your authentication policy (it might be different from this example):





    Note: This condition is based on URLs, basically other conditions such as header fields are also possible - it depends on the needs.



    Step 3: Commit your changes

    Note: This option applies also to other identification policies (IP, Basic)

  • Software Version
    9.x

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

    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    .


    Execution: 0.047. 8 queries. Compression Disabled.
    Powered by InstantKB.NET