6.02 Web Player Security

[erblock]

I'm a little confused on the Web Player security for Lookout 6.02.

I read that the player defaults to level 0 [nobody] access unless a copy of the lookout.sec file is used (which was not available...intentionally), yet when I use a web player client, it has full control access on the server process.

How do I use the network security configuration to prevent writing anything unless a lookout.sec file and login is present on the player client?  Do I have to go into each server process and make everybody have only read access and then give other users/levels write access as appropriate.  Does the Proxy setting (guest with or without a password) play into player client security also?  Are there conditions that will reset the default network security settings in a process I should know about such as process renaming, etc?  I would not want to find out that my secure process was suddenly non secure due to some caviat.

Thanks,

Ed

Message Edited by erblock on 12-16-2005 02:26 AM

[Prashanth]

Hi Ed,

You should be able to force the remote client to download the Lookout.ini file with default login settings to Lookout player. Please take a look at this link for more information on how to download lookout.ini file. <http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/1c39c87fd53373eb86256a40005...>

Couple of other things that can help:

You can restrict access to the html through web server authentication
Also you can use password protected buttons.

Chapters 10 and 12 of the Lookout developer's manual has more information on implementing security options in Lookout. https://www.ni.com/docs/en-US/bundle/371382a/resource/371382a.pdf

Have a great day!

Regards,
Prashanth