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 Security
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 Security
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 » Users and Authentication » INFO: HTTP Error 553 due to Authentication Failure

INFO: HTTP Error 553 due to Authentication Failure

Expand / Collapse
Show/Hide Article Tools


  • Description
    After a new installation of VSOS 9.0, all users cannot browse to the Internet.

  • Symptoms
    All users get HTTP Error 553 - Internal Server Error.
    In the log viewer of the Management Console, you can see that the transactions failed at the authentication handshake phase:


  • Cause
    In self-authentication / self-redirection authentication method, the scanners perform the authentication in front of the external authentication server (usually AD server).

    In order to perform this kind of authentication, the scanners should be able to reach the external authentication server/s.
    However, usually the domain controllers of the external authentication server are written in their relative / host name format, not in their FQDN (Fully Qualified Domain Name).

    In case the organization's domain is not configured in the DNS settings of the Vital Security Web Appliance, the scanners will not be able to resolve the domain controller name, and the self-authentication will fail.


  • Solution
    Define the organization's domain name in the DNS settings via the limited shell
    1. Access via SSH to the limited shell of the policy server.
    2. Type config_network -> Y -> choose option 4 (DNS) -> 1 (Change Search) ->  Type your domain -> Q -> Y


  • Software Version
    9.0

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

    To contact Trustwave 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.063. 9 queries. Compression Disabled.
    Powered by InstantKB.NET