Yes Sir. Thats how it used to work with the old control.
Ex. mswebbrowsercontrol.navigate(url, 0, '_self', data, headerparams) The headerparams will have the BASE64encoded creds and the browser navigates to the page directly(something like autologon). No login window gets displayed and the method has more control to this.
Also, fyi, If this new web browser control is based off of CEF libraries, then i am pretty sure CEF supports it as we have implemented an inhouse workaround to solve this issue by using a java wrapper (JCEF) and it doesnt display any login window for authentication. It will be nice to move away from that approach for us and starting using what Appeon has to offer natively.
I saw your ticket today and transferred it to Engineering. I do not believe that the R2 version of the control has this capability. However, it does not mean that the next January beta might not. Let's see how Engineering responds to your question as they know the upcoming features that are currently not in the R2 beta "preview" release.
if I try to call a webpage that requires basic authentication with the new webbrowser control I get back a 401 (Unauthorized) page because of missing basic authentication. (Microsoft Webbrowser control shows a dialog to enter the credentials is this case.)
I want to specify the credentials anyway programmatically so I can access the website using the new browser control.