So long as either the DHCP lease never expires on those client machines, or static IP’s are assigned to them all, that would work.
I still wonder why they would be letting web traffic in at all … unless they perhaps host their own site to the outside world. And it still seems that it might be easiest to use a custom http port for this Servoy server (or am I wrong in thinking this is possible?) and close those ports on the firewall…
good luck, let us know what works for you (doubtless many of us will have the same type of request from a client some day). Thanks, Westy.
Westy:
I have a customer who only wants to allow his employees to access our solution from the computer they use in his office.
I did it this way:
-extra field in user table: key_needed, default value 0
-extra field in user table: key_installed, default value 0
When a user logs in and key_installed == 0 and key_needed == 1, a file is written to the home folder (.servoy\willcom.key) and key_installed is set to 1.
When a user logs in and key_installed == 1 and key_needed == 1, we check the existance of “willcom.key”. If not, a message is displayed “You cannot login on this computer…”
If the user changes computer, the administrator can set “key_installed” to 0, and make sure this user logs in first at the office.
When a user calls the office “I’m sick at home and want to login to check some things,…”, the administrator can temporarily set key_needed to 0 (check box).
Stef:
When a user logs in and key_installed == 0 and key_needed == 1, a file is written to the home folder (.servoy\willcom.key) and key_installed is set to 1.
Well, this is interesting and is a possiblity I did not know about.
Here’s a bunch of Q’s that come to mind, if you have time …
In what directory path does one find this “home” folder named “.servoy”? Or do you mean it is located as a hidden directory within the user’s own home directory (“~”)
I know the leading “.” on a filename or folder makes it hidden on OS X … does your answer also apply to other platforms?
If the Servoy Client application is always accessed via WebStart and the option to save the jnlp is disabled, does this method still work? (i.e., Does this .servoy directory still exist?)
It seems a very nice way to get around the issues of multiple NICs and dynamic IP addresses. I was thinking it might work well to grab the serial# of the computer itself, but I don’t know if Servoy has access to that info from the client OS. Storing a simple binary key seems superior.
TIA for shedding light on this area in which I am completely “ig’nant”
kazar
PS: Another, off-topic, question: Is there a way on Mac OS X to find and see hidden directories and files? On Win I just change the options in the Explorer window. On my Macs I find I can only locate hidden files using the built-in (awful) search mechanisms if I know the name of the file in advance. However, although I do have a copy of Servoy Client saved to my desktop, I cannot locate any “.servoy” directory anywhere on the hard drive by typing in a find for filename starts with .servoy
In what directory path does one find this “home” folder named “.servoy”? Or do you mean it is located as a hidden directory within the user’s own home directory (“~”)
Check out plugins>file>gethomedirectory
If the Servoy Client application is always accessed via WebStart and the option to save the jnlp is disabled, does this method still work? (i.e., Does this .servoy directory still exist?)
Don’t know, have to check it out… You’ve got a point there
PS: Another, off-topic, question: Is there a way on Mac OS X to find and see hidden directories and files?
If the Servoy Client application is always accessed via WebStart and the option to save the jnlp is disabled, does this method still work? (i.e., Does this .servoy directory still exist?)