Recommendations while protecting dll files in a web application using Envelope

Following are a few recommendations while protecting dll files in a web application using Envelope:

1. Change the ‘Message output mode’ to ‘eventlog’ or ‘standard error log’:

The ‘Message output mode’ in envelope is set to ‘window’ by default. In case a web application hosted on servers such as IIS, tries to display error through a dialog box, the server returns the error message ‘Unable to load modal dialog box’.

So, it is recommended, to change the message output mode to ‘eventlog’ or ‘standard error log’.

2. Copy supporting files in System32 or any other %PATH directory:

When a protected method is called, sometimes the running process (server exe) is unable to locate the supporting files that are present with the protected dll and the web page does not load as it is still searching for the supporting files. This leads to ‘request timeout’ error as the files are not found.

It is recommended to copying the following files in System32 or any other %PATH directory-

  • hasp_rt.exe
  • hasp_windows_xxxxx.dll
  • hasp_windows_x64_xxxxx.dll
  • haspdnert.dll
  • haspdnert_x64.dll

3. Using different feature id at global and feature level:

In case same feature is used for global and method level login then by default, the license checking frequency is set to ‘Once per program’ .Hence license will be checked only for the first time protected method is called.The license will not be checked again until the server is restarted.

 To overcome this, it is recommended to use different feature id’s for global and feature level login.Using a different feature id will allow us to set the frequency to ‘Everytime’ and hence license would be checked everytime a protected method is called.