Page 1 of 1

Locking down Settings?

Posted: 20 May 2020, 20:40
by javaapp
Is there any facility for restricting the user's ability to make changes in the OpenWebstart Settings?

OpenWebstart will be deployed in a customer location; installed by system administrators. It is OK for these admins to have full control over the settings. The end-users, however, should be limited in what they can do in the Settings -- perhaps only allowing such action as enabling debug logging, etc.

Is this currently possible with OpenWebStart? If not, is it doable in a future release?

Re: Locking down Settings?

Posted: 20 May 2020, 22:01
by Stephan Classen

The settings are stored in a property file in the user home.
But there is the possibility to configure system settings which take precedence over the user settings.
Also in the system settings an entry can be locked. This prevents the user from changing such an entry.

Here is a starting point: ... figuration

Please ask if you have more questions

Re: Locking down Settings?

Posted: 21 May 2020, 00:37
by javaapp
Thanks for the speedy reply! The ability to define properties centrally and to lock them down sounds like just what we needed!

Our client will need to perform/script the step of creating the %windir%\Sun\Java\deployment\deployment.config file right? And then also to create the actual properties file referred to by that deployment.config - though that sounds like a simple file copy of a pre-created properties file, or perhaps that file can be installed centrally in a shared directory on the network?


Re: Locking down Settings?

Posted: 21 May 2020, 01:33
by Stephan Classen
Both files are simple text files. So yes you can pre-create them and simply copy them over to every machine.
OWS does not provide any scripts or other features to setup the needed files for a system wide configuration.
We found that most of our customers already have some means for rolling out configurations on their computer.

The URL in the deployment.config file can point to a property file hosted on a server.
This gives the additional advantage that there is a single property file to update in case that the settings need to be changed

Re: Locking down Settings?

Posted: 30 May 2020, 00:55
by javaapp
And I assume these files are proper java properties files, so we can use # comments in them?

Re: Locking down Settings?

Posted: 30 May 2020, 10:33
by Stephan Classen
Yes, all files are read using the method Properties.load()