Putty Returns Error "Proxy error: 407 Proxy Authentication Required"

Available Languages

Download Options

  • PDF     (2.7 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (84.1 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (65.8 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:July 16, 2014
Document ID:117948

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Contents

Problem

Symptoms: When using Putty to tunnel (CONNECT) through the WSA, you receive "Proxy error: 407 Proxy Authentication Required", even after including a username / password in the Putty configuration.


Environment: Cisco Web Security Appliance (WSA), all versions of AsyncOS

Solution

Putty only supports HTTP Basic authentication. It does NOT support NTLM authentication. If the WSA is configured for NTLM authentication only, Putty will return this error message. 

If WSA is configured to use 'NTLMSSP or Basic' authentication scheme, then authentication should work properly.

On AsyncOS versions 7.x and above, the 'NTLMSSP or Basic' authentication scheme is configured in Identities under GUI --> Web Security Manager --> Identities --> "Define Members by Authentication" section.

Revision History

Revision Publish Date Comments
1.0
16-Jul-2014
Initial Release
TAC Authored

Contributed by Cisco Engineers

  • Josh Wolfer and Siddharth Rajpathak
    Cisco TAC Engineers.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products