03-23-2014 06:09 PM
Is there a "best pratice" for implementing application security/authentication for a labview application developed to run on a windows platform? We would like to know what our options are to secure which users in our office can run which test suites or whether they are permitted to run the application at all.
Thanks..
03-24-2014 05:59 PM
Typically we recommend implementing some sort of authentication scheme at run-time, however the implementation of that is up to you. There are a variety of examples posted on password protecting LabVIEW built applicaitons. Here are a few of them, hope this helps! The one we recommend is the first option, but some of the other examples offer more functionality and flexibility.
Password Protect LabVIEW Applications at Run-Time
http://digital.ni.com/public.nsf/allkb/A3A3312AAEF4CC5286257558007E8B22
How to create login and password for my application
http://forums.ni.com/t5/LabVIEW/how-to-create-login-and-password-for-my-application/td-p/787166
LabVIEW and Windows Authentication
http://lavag.org/topic/15260-labview-and-windows-authentication/
Hope this helps!
03-25-2014 08:57 AM
Thanks for the direction. The first two examples would provide the authentication we are looking for but not the "hard coding" of userids or password into the program logic. The last example is a bit closer in that it allows us to externalize these artifacts but requires some adminiatration. For us (a small startup) this is not an issue currently.
Thank again.