09-24-2007 04:38 PM
09-24-2007 10:48 PM
09-25-2007 04:13 PM
09-26-2007 11:37 AM
Thank you Andy and John for your helpful suggestions. We have decided to go with a third approach that is inspired by both of your suggested approaches. There will be a "top-level" executable, "Index.exe", that will be used for logging in and out and for launching the other executables. Each of the other executables will use VI Server to monitor a hidden indicator on Index.exe to find out the currently logged in domain/user. This approach does require a slow poll, however, there is an added advantage: The executables can be programmed such that should the Index.exe close or be abruptly ended through the Windows Task Manager, the other executables will revert to (Nobody) being logged in.
Unfortunately, the suggested approach of using VI Server to programmatically log in to another application does not appear to work, at least not in LV 8.2.1 from LabVIEW to an executable. We were able to access non-security application properties such as "App.Kind" and "App.Name" but the security properties and methods appear not to be accessible between applications. Such attempts result in Error 1032, "VI Server access denied."
A suggested improvement to the NI security model would include a domain setting in the NI Domain Account Manager such that an NI domain login could have a computer-wide scope and not just an application-wide scope. Such an improvement would facilitate the ability to develop modular applications that involve multiple executables interacting with one another and in a secure environment.
Thanks again for the help.
Chris White, ThinkG Consulting LLC
09-28-2007 10:52 AM