I would like to remotely control a LabVIEW application. Is it possible to create multiple different passwords for different users

[barthol]

We are an educational istitution and we intend to use LabVIEW for e-learning. We need to assign a differnt password to a number of students and let them log in (through internet) in a remote control application. Is it possible right after the experiment to e-mail to each student a report conserning his experiment. The e-mail should correspond to the specific student ID.

Thank you

barthol

[Zvezdana S.]

Barthol,
How do you plan to control a LabVIEW application remotely? Is it through the VI Server or with the remote panels?
In either case, you would need to create a login VI that would check for the passwords. It should have a list of passwords, each associated with (maybe) the machine ID. When the run the login VI, it would get the machine IP address for example. The student then needs to enter the password that matches that IP address. The login VI would then check if the two match.
I attached an example of Implementing Remote Panel Security with a Login.

This example illustrates a technique that can be used to add security to your remote panel applications. The example consists of two VIs - A "Login" VI that verifies a user's name and password, and a "Main" VI that the user can access only after logging in. The user is required to login with Remote Panel Login.vi before they can access main.vi.

In order to setup this example, both VIs should be configured for a remote panel connection via the Embedded option in the Web Publishing Tool. Remember that the VIs must be in memory on the server machine to browse to it on another machine.

After configuring the VIs with the web publishing tool, you should first browse to the "Remote Panel Login.vi" and run it. When this VI is run, remote panel access is given to everyone but they can only view and control this VI. If the user successfully logins by supplying the Username of NI and password of labview (both are case sensitive) then remote panel access is switched so only the ip address specified has access and they can only access main.vi.

After gaining access, the user should browse to and run the main.vi. They will only be able to browse to the VI once since permissions will be reset in the code. In order to browse to main.vi again, the user will need to login.

The other attached VI simply lets you specify user ID and password. The Verify Login.vi then searches a table of employee information for a match. If a match is found, then the employee is verified, and the employee name is returned.

To email reports, you can either use the Internet Toolkit, that has email VIs, or using ActiveX Automation calls to outlook. The outlook must properly be configured before using this VI. If your mail server requires password, you would be automatically prompted for that once you run the VI. This VI is also attached.

Zvezdana S.
National Instruments

[Belur]

I would appreciate more explanation. Is the 'main.VI' called automatically when the user/password is verified? Is it supposed to be seen on the remote panel on the client browser? In the above, when you say 'both VI' which of the two VI's among 'login.vi' and 'main.vi' and 'remote Panle login.vi' are you referring to? Any help will be greatly appreciated.

[Ya-hoo]

Hi there,

I tried the Remote Panel Login examples which were attached by Zvezdana S. It works when main.vi running in Labview enviroment. But after I created a executable file of main.vi, it didn't work, the Web Server: Browser Access couldn't be changed from "remote panel loging.vi".  BTW, both main.exe and Remote Panel Login,vi run at the same PC.

I am confused by ports number, ini file.

How could I set port number when they are running at the same PC?

When I built the executable file, ini file was built in as a support file. should ini file be changed on fly when you change Tools->options setting at executable.

In Remote Panel Loging.vi, there is a application property node, do I have to reference it to localhost?

Thank you very much for the reply.