Logo
My Account |  Site Map | Contact Us  
Welcome Guest Search | Active Topics | Sign In | Register

Windows Authentication Options
PraKom Software GmbH
Posted: Thursday, July 23, 2020 2:49:20 AM
Rank: Member
Groups: Member

Joined: 7/17/2020
Posts: 14
Hi,

we replaced .net WebBrowser now with EO WebControl - one issue we have now is a website which uses windows authentication. that worked fine with WebBrowser - but now with EO WebControl the user is getting constantly a credentials popup - are there any settings we have to make to provide windows authentication support?
PraKom Software GmbH
Posted: Tuesday, July 28, 2020 6:02:47 AM
Rank: Member
Groups: Member

Joined: 7/17/2020
Posts: 14
Any info on this?
eo_support
Posted: Tuesday, July 28, 2020 10:30:43 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 22,324
Hi,

Sorry about the delay. Please check whether you have explicitly created Engine object or have recreated/unload AppDomains in your application. EO.WebBrowser does support Windows Authentication, and the user credential information is cached per browser engine once entered until that engine is unloaded. This means:

1. If you have multiple Engine instances, then they will not share the credentials. By default, each AppDomain has a single Engine object. So if you have multiple AppDomain, then you will have multiple Engine objects. Additionally, you can also explicitly create additional Engine object;
2. If the Engine object is unloaded, then user will need to re-enter the credentials. Typically the Engine object is unloaded when your application closes. However since Engine object lives inside an AppDomain, if you unload an AppDomain, it will be unloaded as well. An Engine object can also be unloaded by explicitly calling Engine.Stop. In any of those cases, the credential cache will be lost and the user will need to re-enter the credential next time;

Hope this helps. Please feel free to let us know if you still have any questions.

Thanks!
PraKom Software GmbH
Posted: Friday, July 31, 2020 4:44:00 AM
Rank: Member
Groups: Member

Joined: 7/17/2020
Posts: 14
Hi,

thank you - the problem is more here that the user HAS to enter his credentials. with the browser he just navigate to the site - and he is automaticly logged on with windows auth - with the EO WebControl has has to enter credentials. is there anything we miss?

thx
eo_support
Posted: Friday, July 31, 2020 10:59:49 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 22,324
Hi,

It shouldn't. EO.WebBrowser would use the current user's context to authenticate first. If that fails, then it will trigger NeedCredentials event. You may want to check two things:

1. Whether you are using the latest build;
2. Whether your application is running under a different user context;

Thanks


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.