Home/ Questions/Q 6924367
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T10:39:16+00:00

I have a Windows Forms app targeting .NET 2.0. I’m attempting to add a

  • 0

I have a Windows Forms app targeting .NET 2.0. I’m attempting to add a single sign-on feature via the SAML 2.0 protocol, for which the most efficient apparent solution was an embedded web browser.

I’ve verified using a dummy app containing only a WebBrowser control that the NTLM exchange does take place. However, when I embed apparently the same control into the larger application, the browser doesn’t respond to the initial HTTP 401 challenge and instead redirects to IE’s “Navigation Canceled” page.

The Googles have not been forthcoming, and I’m puzzled at this behavior. Can anyone shed some light on what might be inhibiting the WebBrowser’s credential negotiation?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I discovered the answer during a line-by-line comparison between the (working) test app and the (not working) full app.

    The key to enabling NTLM negotiation for me was to set ScriptErrorsSuppressed to false. I had intended to hide Javascript error popups from our users, but suppressing those also suppresses credential negotiation. Go figure.

    • 0