Remote Panel Access

[Alan Cheuk]

Hi

I am using LabVIEW remote panel that I will open several VIs to let web browser remote control them. So that all of these VIs are already in the "VI Access List". But in the beginning, nobody is in the "TCP/IP Access List". What I want to do is to add browser's IP address to "TCP/IP Access List" if he pass the authorization. However, I find a problem that if the browser's IP address is not already in the "TCP/IP Access List", he also cannot access my authorization part through a web browser. That means in final, nobody can add in the "TCP/IP Access List". Does anyone have any other solution to achieve an authorization in remtoe panel?

Beside, I am also using HTTP Server (In Internet Toolkit) to publish the snapshot of a VI. Does anyone know how can I get the IP address of the connected browser? (I know how to do it in remote panel web server but don’t know in HTTP Server).

Thanks

[Robert M]

One idea would be to give everyone access but only allow them to run your other VI's once they have passed your authorization VI, sort of like a "login" for your server.

[Johnner]

Alan,

Attached is an example that should do what you are after. Here's the little description I included in the zipfile; I also included a screenshot if you're not using 7.1:

--------
As of LabVIEW 7.1, there is no LabVIEW functionality to make some VIs
available to all remote panel Web clients while restricting other VIs to
a smaller list of clients. This prevents a developer from creating a
remote-panel authentication VI that dynamically adds clients to the
access list.

This example demonstrates how to use the Internet Toolkit CGI VIs to
dynamically add client IP addresses to LabVIEW's Web Server Browser
Access List. This enables a developer to programmatically authenticate a
client and add it to the access list for remote viewing and controlling,
instead of manually adding the client's IP address to the access list.
--------

CGI represents a nice alternative sort of API that allows you to do helpful things with LabVIEW. Ultimately, there's no real security here, because the login info will be transmitted in the clear, but it's presumably better than no security at all.

Regards,
John