title: C# WebBrowser - Application-wide policies that impact security
body: <p>I developed a plugin that works on a 3rd party application. That 3rd party application has the ability to start up two different ways - it can either load up in Winforms mode or it can load up in WPF mode. That application only accepts plugins written for Winforms, and in WPF mode, it just wraps the plugin in a WinFormsAdapter:</p>
  
  <p><a href="https://i.stack.imgur.com/aDdSz.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/aDdSz.png" alt="Same plugin within Winforms vs. WPF app"></a></p>
  
  <p>Now, MyPlugin contains a WebBrowser that seems to work pretty reliably in the Winforms mode/app. However, the EXACT same plugin/code in WPF will occasionally trigger security warning popups (e.g. one example was popups about certificate revocation info not being available). These popups in turn can impact the code's ability to work with secure cookies. I suspect the warnings themselves are legitimate and maybe they were bypassed before somehow, but it's puzzling as to why there is any difference at all.</p>
  
  <p>The 3rd party app's developer has told me that there is one piece of their system that implements IHttpSecurity, but it shouldn't have any relation to my plugin. Are there any known policies or settings that are process-wide or application-wide, where the 3rd party dev might be setting something that is influencing the WebBrowser in my plugin?</p>