How should I allow access to my Java Web Start program?
I am managing the development of an application that will be deployed using java web start. I only want each of my client's workers to be able to initially download the app and log in from their office location, but I do not want them to have the ability to access the application from home, or any non-clients to access it. How should I set up the authentication process? Getting the IT department of each client more involved in the installs is a possibility as well. Any help would be appreciated.
[508 byte] By [
cactus12a] at [2007-10-3 8:09:26]
If a user installs the software in their lap-top at work,
then jumps on a train (bus, ferry, whatever..) to travel
home, does operation of the software on the lap-top
on the transport come under 'work' or 'home' use?
What if I were to set it up for remote use off the
work based main-frame? That way, the software
is working on the 'office computer' as per agreement,
whereas I am using it from out on the back verandah,
while having a relaxing breakfast..
(Of course, another way to express is that*, is..
"Who thought up this ridiculous distribution scheme?!?")
* I.E. The way I'd look at it, If I were an end-user,
examining this software for potential evaluation/use..
Thanks for your reply.
The whole point of my post is to avoid a situation where people say "Who thought up this ridiculous distribution scheme?!?" :)
Anyway, laptops are not an issue - none of my clients give laptops to their workers. I'd rather avoid a mainframe setup because the beauty of Java Web Start is that it doesn't require the normal installation procedure at each client, and I'd rather focus my effors in sales and marketing for my small company rather than running around doing installs etc.
Basically I want to create the easiest installation and maintenance procedures possible (trying to avoid client certificates) while still:
- Only allowing access to installing/using the program to client workers while running the application at the office
- Giving out separate ID's to each worker at each client (need to track activities in application by worker)
Any ideas would be greatly appreciated :)
I am assumming the application accessess a database or something esle on the intranet.
If it does then they can't use it out of the office (unless they VPN in or PCanywhere, etc.).
If not what does it do? (Maybe you can make it require the company network by checking for a file on a network drive or something?)
