how to add user in NI Security programatically?

[samriddh]

hi,

i had created a project using NI Security features.

it has four security levels like administrator, engineer, operator & guest.

the administrator has the right to change the password of any existing user.

but i want that the administrator should be able to create a new user or group or delete a user or group as he has the right to change password.

i want to do this programatically.

does anyone knows how to accomplish it.

the appropriate reply will be highly appritiated.

samriddh sarbalhi

sarbalhi.samriddh@gmail.com

[Pie56694]

Dear Samriddh,

The Domain Account Manager provides access to NI Security features.  Access the Domain Account Manager from the Project Explorer, Block Diagram or Front Panel from Tools >> Security >> Domain Account Manager.  Several NI Security properties and methods may be accessed programatically.  To access these methods and properties, use the Application Control pallet from the block diagram.

Start with a VI Server Reference, change the reference from This VI to This Application.  Wire the reference output of the VI Server Reference to the reference input of a Property or Invoke Node.  Here is a screen shot of the NI Security methods and properties included with LabVIEW 8.5.1 PDS.



The LabVIEW Datalogging and Supervisory Control (DSC) Module provides additional Security VIs.  Notice that neither the Application methods/properties nor the DSC module provides VIs to programmatically add or delete uses and groups as you would like.  The work-around is to launch the User Manager programatically in LabVIEW.  Use a System Exec.VI with a constant string input to the System Exec's Command Line input node.  The string to launch the User Manager program is C:\Program Files\National Instruments\Shared\Logos\usrmgr.exe.

Please refer to the following documents for more information:
Using the Domain Account Manager (Windows)
Enhanced System Security with the LabVIEW Datalogging and Supervisory Control Module

Please post back with any additional questions.  Thank you for using the NI forums.


Message Edited by Pie56694 on 05-28-2008 02:02 PM

Message Edited by Pie56694 on 05-28-2008 02:04 PM

[Ben]

Steve,

Blue Property nodes?

Ben

Former resident of Tom's River NJ

[Pie56694]

Dear Ben,

Thank you for bringing up this caveat.  The above screen shot is the full set of NI Security properties and methods in LabVIEW 8.5.1 PDS.  Some (yellow) are public.  Others (blue) are private.  The bottom line for Samriddh is that one cannot create NI Security users or groups programmatically in LabVIEW.

[Andrey_Dmitriev]

Hi, Steve,

One more question. If I using security mechanism provided by DSC, do I need to purchase and install DSC Runtime for deploying my application to the customer PC or not?

best regards,

Andrey.

[Pie56694]

Dear Andrey,

"If you want to run applications built with LabVIEW, the DSC Module, and the LabVIEW Application Builder on a computer without the DSC Module installed, you must install the DSC Module Run-Time System."

Please see the "Considerations for the DSC Module Run-Time System" section of "Release and Upgrade Notes: LabVIEW Datalogging and Supervisory Control Module Version 8.5" (page 6) for more information.  Click here for online pricing for the DSC RT.

Thank you for your question and for using the NI forums.

[Andrey_Dmitriev]

Steve,

Thank you for the answer. But I will follow this document, where NI wrote: "...If the only LabVIEW DSC module VIs your application uses are the Security VIs, you can distribute those VIs without using the LabVIEW DSC module Run-Time System...", then license is not required, isn't?

So, my application developed with DSC Module, but Security VIs from DSC toolkit distributed manually to the target PC according instructions above. Do I still need to purchase LV DSC Run-Time License for the target PC in this case?

best regards,
Andrey.

[Pie56694]

Dear Andrey,

The Knowledge Base referenced pertains to LabVIEW 6.x.  The DSC help page referenced by the KB does not exist for DSC 8.5.  Additionally, the lv_init.vi referenced by the KB does not exist for LabVIEW 8.5, so it is not possible to use this KB for a LabVIEW 8.5 application that only uses DSC security VIs.  The Tag Configuration Engine was completely redesigned with LabVIEW 8.0.  Perhaps if you're using an older version of LabVIEW and DSC, this work-around is still possible.