Table of Contents
- Getting Started
- EO.Pdf
- EO.Web
- EO.WebBrowser
- EO.Wpf
- Common Topics
- Reference
- .NET API Reference
- EO.Base
- EO.Base.UI
- EO.Extensions
- EO.Pdf
- EO.Pdf.Acm
- EO.Pdf.Contents
- EO.Pdf.Drawing
- EO.Pdf.Mvc
- EO.Web
- EO.WebBrowser
- EO.WebBrowser.DOM
- EO.WebEngine
- EO.WebEngine
- Classes
- Cookie Class
- CookieCollection Class
- CookieManager Class
- Cursor Class
- Engine Class
- Engine Class
- Engine Members
- Properties
- Methods
- Methods
- CleanUpCacheFolders Method
- Create Method
- FromID Method
- FromName Method
- GetAll Method
- GetChildProcessIDs Method
- Start Method
- Stop Method
- Events
- EngineEventArgs Class
- EngineOptions Class
- WebViewOptions Class
- Enumerations
- Delegates
- EO.WinForm
- EO.Wpf
- EO.Wpf.Gauge
- EO.Wpf.Gauge.Shapes
- EO.Wpf.Primitives
- EO.Wpf.Themes.Aero
- EO.Wpf.Themes.Classic
- EO.Wpf.Themes.Luna
- EO.Wpf.Themes.Metro
- EO.Wpf.Themes.Royale
- JavaScript API Reference
- .NET API Reference
Engine.Start Method (WindowsIdentity) |
Starts the engine using a specific user for Windows authentication.
Syntax
Parameters
- user
- The specific user the engine should use to authenticate with the server.
Remarks
The vast majority of the engine code will always run under the process user account. The user provided here is only used for Windows authentication purpose.
You should avoid the underlying user token used by user from being closed during the life time of the engine. For example, the following code would be problematic because the underlying user token is closed immediately after the engine.Start returns:
using (WindowsIdentity user = new WindowsIdentity(userToken)) { engine.Start(user); }
To avoid this problem, you can keep user in a variable and only disposes it when the engine stops.
See Also