Question
Securing access to WebHelp output
I am after some advice from those with experience on securing
access to Webhelp ouptut. What we want is to control user access to
the server to only those with the product installed - a Marketing
decision designed to protect our intellectual property. However
each product has a different installation method. Some use an
install shield that can be run by anyone whilst others use a script
run by one of our product consultants.
I know whatever we do will have to be on the application side but I want to suggest that whatever approach is used is as generic as possible. My current thinking is that the webhelp output would be locked down and that each product install would include read access rights to the help. This could be added to any install script and also any install shield. Obviously we would have to make our users aware via the install docs about the access changes.
Does this sound like a good approach or is there a better way of achieving the same thing?
I know whatever we do will have to be on the application side but I want to suggest that whatever approach is used is as generic as possible. My current thinking is that the webhelp output would be locked down and that each product install would include read access rights to the help. This could be added to any install script and also any install shield. Obviously we would have to make our users aware via the install docs about the access changes.
Does this sound like a good approach or is there a better way of achieving the same thing?
AdChoices