This access token is only created when the user's account name and password are supplied (at login, for RunAs, and so on). In the Windows world, in order to perform any action as a user (whether it's running a program, authenticating against AD or anything else), you require an access token, which is used to identify and authenticate the user's access/privileges. (There aren't even any clever workarounds or hacks to circumvent it as there usually are - this one's just far too deeply rooted to get around.) I can't find the document or article at the moment, but not allowing sudo-style user impersonation functionality in Windows was a deliberate design decision way back in the earliest days of the NT kernel, and as a result, we're very much stick with it. There's no sudo equivalent, or even approximation in Windows. Windows does not offer the type of user impersonation capability you're asking about here.
0 kommentar(er)
