Click here to Skip to main content
Licence 
First Posted 24 May 2004
Views 174,985
Bookmarked 65 times

RunAs Class

By | 14 Feb 2005 | Article
Class that wraps CreateProcessWithLogonW as well as a simple control that makes use of the RunAs class.

Sample Image - RunAs.jpg

Introduction

There are three projects in this solution: RunAs, UseRunAsControl, and ProcessToStart. RunAs is the focus of this solution; it contains the class that wraps CreateProcessWithLogonW. UseRunAsControl defines and makes use of a simple control implementing the RunAs class and is meant to test and show its functionality. ProcessToStart is simply a form that shows the domain and username of the user whose syntax it is running under. This is merely there to start with the UseRunAsControl to demonstrate its functionality.

Demo

To see the solution in action, grab a second set of credentials (make some dummy ones on your local machine, perhaps). Run UseRunAsControl.exe and provide the credentials. Click on "Command..." and browse to ProcessToStart.exe. Click on "Run Command". Provided the credentials are correct, you will see a MessageBox containing the process ID of the new process. ProcessToStart will display the username that it is running as. If the credentials that UseRunAsControl.exe is running under has enough privileges, when you close ProcessToStart, you will see another MessageBox notifying you that the process has ended. If the user does not have privileges to the new process, you will see a MessageBox notifying you of this, and when ProcessToStart.exe exits, you will not receive any notice.

Class Usage

Using the RunAs class is simple. Add a reference to the assembly and include the namespace VastAbyss. There is an overloaded static method named StartProcess in the class. This simple overload provides standard functionality that starts the executable as the user and loads the profile. A word of caution with using this method is that if the command line is C:\Program Files\Some Directory\Some.exe, if a Program.exe exists in C:\, it will be started and this may be seen as a security flaw. It is due to the way that CreateProcessWithLogonW parses and searches the command line (space-delimited). To avoid this, surround the command line in quotes. All of the overloads return a Process. If the process failed to start, it will be null and a Win32Exception will be thrown. Below is a sample of the simple usage:

  string username = "SomeUser";
  string domain = "SomeDomain";
  string password = "I'll never tell!";
  string commandline = "\"C:\\Program Files\\Some Directory\\Some.exe\"";

  // Resulting string is
  //  "C:\Program Files\Some Directory\Some.exe"
  // with the quotes included.
  try
  {
    Process proc = RunAs.StartProcess(username, domain, password,
                                                    commandline);
    try
    {
      proc.EnableRaisingEvents = true;
      proc.Exited += new EventHandler(processExited);
    }
    catch
    {
      //The process started but you don't have access to it.
    }
  }
  catch (Win32Exception w32e)
  {
    // The process didn't start.
  }

To avoid the security risk of using command line, use one of the other overloads of StartProcess() to provide the executable in appname instead of command line (command line must be used to provide parameters to the executable if needed; i.e., c:\myapp.exe /q /t). These overloads provide many more options for creating the new process. Enums are provided for supplying the values of the flags. Additional overloads can easily be added to provide full control over creating the new process. The struct definition for StartUpInfo is public and can be used with the last overload to provide the maximum amount of control.

I have added a default constructor to the RunAs class. This constructor initializes the properties to the following values: UserName (System.Environment.UserName), Domain (System.Environment.UserDomainName), Password (empty string ""), ApplicationName (CurrentProcess.StartInfo.FileName), LogonFlagsInstance (LogonFlags.WithProfile), CommandLine (System.Environment.CommandLine), CreationFlagsInstance (CreationFlags.NewConsole), CurrentDirectory (System.Environment.CurrentDirectory), Environment (IntPtr.Zero), ProcessInfo (new ProcessInformation instance), StartupInfo (new StartUpInfo instance with the following values set: cb is set to the size of the new instance, dwFlags is set to StartUpInfoFlags.UseCountChars, dwYCountChars is set to 50, lpTitle is set to CurrentProcess.MainWindowTitle). After initialization, these values can be changed and the non-static method StartProcess can be called.

Control Usage

I will leave the below code included although the focus of this project is to implement the RunAs class and not this control. This control merely serves as an example of how the RunAs class can be used. I removed the RunAsControl from the RunAs project and placed it in the UseRunAsControl project.

The RunAsControl can be quickly added to a Windows Form and the four events wired up. That's all there is to it. Below is an example usage:

  RunAsControl m_runAsCtl = new RunAsControl();
  m_runAsCtl.ProcessStarted += new ProcessStartedEventHandler(m_pStarted);
  m_runAsCtl.ProcessFailed += new ProcessFailedEventHandler(m_pFailed);
  m_runAsCtl.ProcessEnded += new ProcessEndedEventHandler(m_pEnded);
  m_runAsCtl.ProcessAccessFailed += 
      new ProcessAccessFailedEventHandler(m_pAccessFailed);

Comment Disclaimer

I referred to the MSDN documentation for the CreateProcessWithLogonW, PROCESS_INFORMATION, STARTUPINFO, etc... functions, structs, and constants. Most of the comments in the source code are either direct quotes from this documentation or adaptations of information from that documentation.

Thanks

I would like to thank those who provided feedback to this project. I have incorporated the suggestions and fixed the bugs that I found. I hope that this makes the project better, but if there are still things that you think are wrong with it, I welcome more constructive criticism.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here

About the Author

Dewey Vozel

Web Developer

United States United States

Member



Sign Up to vote   Poor Excellent
Add a reason or comment to your vote: x
Votes of 3 or less require a comment

Comments and Discussions

 
You must Sign In to use this message board. (secure sign-in)
 
Search this forum  
 FAQ
    Noise  Layout  Per page   
  Refresh
GeneralSpecific issue PinmemberSRoyalty5:05 10 Jan '11  
GeneralRe: Specific issue PinmemberDewey Vozel8:29 12 Jan '11  
GeneralLifesaver!!!! Pinmemberlemur6:55 14 Sep '10  
GeneralRe: Lifesaver!!!! PinmemberDewey Vozel1:53 16 Sep '10  
QuestionWhen press enter the app. runs Pinmembermelankolik660:38 10 Sep '09  
GeneralWait Extension PinmemberJoPa33:19 17 Aug '09  
QuestionRunAs error in XP sp2 PinmemberJake1234561:39 5 May '07  
AnswerRe: RunAs error in XP sp2 PinmemberJake1234562:23 5 May '07  
AnswerRe: RunAs error in XP sp2 PinmemberDewey Vozel7:54 5 May '07  
GeneralRe: RunAs error in XP sp2 PinmemberJake1234562:31 7 May '07  
GeneralRe: RunAs error in XP sp2 PinmemberNaresh N Jamadagni16:42 6 Nov '08  
Questioncan u runas user from other computer? Pinmembermikilior20:52 17 Jul '06  
QuestionCan I??? Pinmembertknman07008:10 19 Jun '06  
AnswerRe: Can I??? PinmemberDewey Vozel13:38 19 Jun '06  
GeneralRedirecting stdout, stderr, stdin PinmemberEyeHatePickingScreenNames7:40 27 Feb '06  
AnswerRe: Redirecting stdout, stderr, stdin PinmemberDewey Vozel13:20 28 Feb '06  
GeneralLicense PinmemberStefan Rusek3:19 11 Jan '06  
GeneralRe: License PinmemberDewey Vozel12:27 13 Jan '06  
GeneralStarting process from Windows Service Pinmembermrdance7:16 13 Jul '05  
AnswerRe: Starting process from Windows Service PinmemberEyeHatePickingScreenNames7:44 27 Feb '06  
QuestionRe: Starting process from Windows Service PinmemberKlampfi23:23 25 Apr '06  
AnswerRe: Starting process from Windows Service Pinmemberdavelogie2:49 26 Apr '06  
GeneralRe: Starting process from Windows Service PinmemberKlampfi7:46 26 Apr '06  
AnswerRe: Starting process from Windows Service Pinmemberdavelogie8:41 26 Apr '06  
Here's logon stuff. You can add CreateProcessAsUser easy enough. Remember that the lpDesktop member of StartupInfo = "" (not NULL and not "WinSta0\Default") for this application. Good luck.
 

 
#region User Logon
 
///
/// The LogonUser function attempts to log a user on to the local computer.
///

[DllImport("advapi32.dll", CharSet = CharSet.Auto, SetLastError = true)]
private static extern bool LogonUser(String lpszUsername, String lpszDomain, IntPtr lpszPassword, int dwLogonType, int dwLogonProvider, out IntPtr hToken);
 
///
/// The DuplicateTokenEx function creates a new access token that duplicates an existing token. This function can create either a primary token or an impersonation token.
///

[DllImport("advapi32.dll", CharSet = CharSet.Auto, SetLastError = true)]
private static extern bool DuplicateTokenEx(IntPtr hExistingToken, int dwDesiredAccess, ref SecurityAttributes lpTokenAttributes,
int impersonationLevel, int tokenType, out IntPtr phNewToken);
 
///
/// The LoadUserProfile function loads the specified user's profile
///

[DllImport("userenv.dll", CharSet = CharSet.Auto, SetLastError = true)]
private static extern bool LoadUserProfile(IntPtr hToken, ref ProfileInfo lpProfileInfo);
 
///
/// The UnloadUserProfile function unloads a user's profile that was loaded by the LoadUserProfile function
///

[DllImport("userenv.dll", CharSet = CharSet.Auto, SetLastError = true)]
private static extern bool UnloadUserProfile(IntPtr hToken, IntPtr hProfile);
 
///
/// Closes an open object handle.
///

[DllImport("kernel32.dll", CharSet = CharSet.Auto, SetLastError = true)]
private static extern bool CloseHandle(IntPtr handle);
 
///
/// The SECURITY_ATTRIBUTES structure contains the security descriptor for an object and specifies whether the handle retrieved by specifying this structure is inheritable
///

[StructLayout(LayoutKind.Sequential)]
public struct SecurityAttributes
{
public int dwLength;
public IntPtr lpSecurityDescriptor;
public bool bInheritHandle;
}
 
///
/// Profile Info
///

[StructLayout(LayoutKind.Sequential)]
public struct ProfileInfo
{
///
/// Specifies the size of the structure, in bytes.
///

public int dwSize;
 
///
/// This member can be one of the following flags: PI_NOUI or PI_APPLYPOLICY
///

public int dwFlags;
 
///
/// Pointer to the name of the user.
/// This member is used as the base name of the directory in which to store a new profile.
///

public string lpUserName;
 
///
/// Pointer to the roaming user profile path.
/// If the user does not have a roaming profile, this member can be NULL.
///

public string lpProfilePath;
 
///
/// Pointer to the default user profile path. This member can be NULL.
///

public string lpDefaultPath;
 
///
/// Pointer to the name of the validating domain controller, in NetBIOS format.
/// If this member is NULL, the Windows NT 4.0-style policy will not be applied.
///

public string lpServerName;
 
///
/// Pointer to the path of the Windows NT 4.0-style policy file. This member can be NULL.
///

public string lpPolicyPath;
 
///
/// Handle to the HKEY_CURRENT_USER registry key.
///

public IntPtr hProfile;
}
 
///
/// Logon type option.
///

[FlagsAttribute]
public enum LogonType
{
///
/// This logon type is intended for users who will be interactively using the computer
///

Interactive = 2,
///
/// This logon type is intended for high performance servers to authenticate plaintext passwords.
///

Network = 3,
///
/// This logon type is intended for batch servers, where processes may be executing on behalf of a user without their direct intervention.
///

Batch = 4,
///
/// Indicates a service-type logon. The account provided must have the service privilege enabled.
///

Service = 5,
///
/// This logon type is for GINA DLLs that log on users who will be interactively using the computer.
///

Unlock = 7
}
 
///
/// Specifies the logon provider.
///

[FlagsAttribute]
public enum LogonProvider
{
///
/// Use the standard logon provider for the system.
///

Default = 0,
///
/// Use the negotiate logon provider. (WINNT50)
///

Negotiate = 3,
///
/// Use the NTLM logon provider (WINNT40)
///

NTLM = 2,
///
/// Use the Windows NT 3.5 logon provider.
///

WinNT35 = 1
}
 
///
/// Specifies the requested access rights for the new token.
///

[FlagsAttribute]
public enum DuplicateTokenDesiredAccess
{
///
/// To request the same access rights as the existing token, specify zero.
///

SameAsExisting = 0,
///
/// To request all access rights that are valid for the caller, specify MAXIMUM_ALLOWED.
///

MaximumAllowed = 0x02000000
}
///
/// Specifies a value from the SECURITY_IMPERSONATION_LEVEL enumeration that indicates the impersonation level of the new token
///

[FlagsAttribute]
public enum ImpersonationLevel
{
///
/// The server process cannot obtain identification information about the client, and it cannot impersonate the client. It is defined with no value given, and thus, by ANSI C rules, defaults to a value of zero.
///

Anonymous = 0,
///
/// The server process can obtain information about the client, such as security identifiers and privileges, but it cannot impersonate the client. This is useful for servers that export their own objects, for example, database products that export tables and views. Using the retrieved client-security information, the server can make access-validation decisions without being able to use other services that are using the client's security context.,
///

Identification = 1,
///
/// The server process can impersonate the client's security context on its local system. The server cannot impersonate the client on remote systems.,
///

Impersonation = 2,
///
/// The server process can impersonate the client's security context on remote systems. This impersonation level is not supported on WinNT
///

Delegation = 3
}
///
/// Specifies the requested access rights for the new token.
///

[FlagsAttribute]
public enum TokenType
{
///
/// The new token is a primary token that you can use in the CreateProcessAsUser function.
///

Primary = 1,
///
/// The new token is an impersonation token.
///

Impersonation = 2
}

private void LogonUser(String user, String domain, SecureString password, LogonType type, LogonProvider provider)
{
if (password.IsReadOnly() == false)
throw new InvalidOperationException("SecureString not ReadOnly");
 
if (string.IsNullOrEmpty(user) == true || string.IsNullOrEmpty(domain) == true)
throw new InvalidOperationException("No user account specified");
 
IntPtr handle;
IntPtr bstr = Marshal.SecureStringToBSTR(password);
bool result = LogonUser(user, domain, bstr, (int)type, (int)provider, out handle);
Marshal.ZeroFreeBSTR(bstr);
 
if (result == false)
throw new System.ComponentModel.Win32Exception();
 
SecurityAttributes sa = new SecurityAttributes();
sa.dwLength = Marshal.SizeOf(sa);
sa.lpSecurityDescriptor = IntPtr.Zero;
sa.bInheritHandle = true;
 
IntPtr newHandle;
result = DuplicateTokenEx(handle, (int)DuplicateTokenDesiredAccess.MaximumAllowed, ref sa,
(int)ImpersonationLevel.Impersonation, (int)TokenType.Primary, out newHandle);
if (result == false)
throw new System.ComponentModel.Win32Exception();
 
CloseHandle(handle);
handle = newHandle;
 
hToken = handle;
}
 
public void LoadUserProfile(string username)
{
if (hToken == IntPtr.Zero)
throw new InvalidOperationException("User not logged in");
 
ProfileInfo info = new ProfileInfo();
info.dwSize = Marshal.SizeOf(info);
info.lpUserName = username;
info.dwFlags = 1; // PI_NOUI 0x00000001 // Prevents displaying of messages
 
bool result = LoadUserProfile(hToken, ref info);
if (result == false)
throw new System.ComponentModel.Win32Exception();
 
hProfile = info.hProfile;
}
 
internal void LogOffUser()
{
#if false
string identity = WindowsIdentity.GetCurrent().Name;
string threadIdentity = Thread.CurrentPrincipal.Identity.Name;
scriptTask.State.AddMessage(DateTime.Now, string.Format("Logging off user {0} ({1})", identity, threadIdentity));
#endif
 
WindowsIdentity.Impersonate(IntPtr.Zero);
 
#if false
identity = WindowsIdentity.GetCurrent().Name;
Thread.CurrentPrincipal = new WindowsPrincipal(WindowsIdentity.GetCurrent());
threadIdentity = Thread.CurrentPrincipal.Identity.Name;
scriptTask.State.AddMessage(DateTime.Now, string.Format("Identity now {0} ({1})", identity, threadIdentity));
#endif
 
if (hToken != IntPtr.Zero && hProfile != IntPtr.Zero)
{
bool result = UnloadUserProfile(hToken, hProfile);
hProfile = IntPtr.Zero;
 
if (result == false)
throw new System.ComponentModel.Win32Exception();
}
 
if (hToken != IntPtr.Zero)
{
bool result = CloseHandle(hToken);
hToken = IntPtr.Zero;
 
if (result == false)
throw new System.ComponentModel.Win32Exception();
}
 
}
 
#endregion // User Logon
 



QuestionRe: Starting process from Windows Service PinmemberKlampfi3:36 27 Apr '06  

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Mobile
Web03 | 2.5.120529.1 | Last Updated 15 Feb 2005
Article Copyright 2004 by Dewey Vozel
Everything else Copyright © CodeProject, 1999-2012
Terms of Use
Layout: fixed | fluid