Disable IP verifications for individual licenses and allow protected scripts to run on systems with dynamic IPs with Auto PHP Licenser 2.1.

Times goes by… Recently, we announced Auto PHP Licenser 2.0 – the most important update to PHP licensing system since its initial release. Today, you can download Auto PHP Licenser 2.1; yet another upgrade loaded with new features requested by its users. Let’s see some of them!

Option to disable IP verification for individual licenses;

Beside many checks and validations, PHP license manager locks each installation to a specific IP address. For example, if user installs protected script on system with IP address X, and then copies it to system with IP address Y, script won’t even start on second machine. Just as developers would expect, protected script also stops working if user deploys a copy on the same IP address as his first installation, but that’s another story. However, a small number of authors asked us if their clients can install and run protected scripts on systems with dynamic IP addresses. In such situations, clients want to deploy scripts on their local hosts that are connected to the Internet without static IP addresses. In other words, client’s server gets new IP address every time it connects to the Internet.

While such setup doesn’t affect new installations, it can cause minor issues for future verifications. That’s because after client’s server connects to the Internet using new IP address, it doesn’t match IP stored on licensing server. As a result, validation fails and protected script doesn’t work until author updates user’s IP address on his server.

So what’s the solution to protect PHP code?

With this in mind, we published workarounds to this issue on phpmillion’s support forums, so developers can prevent IP check by adding a snippet with extra code to their applications. Starting with Auto PHP Licenser 2.1, authors can manage IP validations without modifying a single bit of code. All they have to do is activate Disable IP Verification option for selected license(s). This option is available in the administration dashboard of PHP license manager, so authors can activate/deactivate it at any time. Furthermore, it applies per individual license. In that case, developers can force full verification for all clients by default and only disable IP check for trusted users who can’t install protected scripts on static IPs for some reason.

If you are in the same boat, be aware that disabling IP verification will reduce overall protection for particular installation.  For this reason, only enable new option if you don’t have another choice. But before you do, contact our support team first! We will provide you with step-by-step instructions on how to protect this particular installation from piracy by changing some other options available in PHP licensing system.

More validations for stronger protection.

Since disabling IP check might reduce overall protection, we greatly improved PHP license management software with the following features:

Additional user request verification and blocking in callback and API modules;

IP resolver verification for licenses that are only valid for real domains;

Additional server response validation in user module;

Important to realize that new features work with all licenses by default, not depending on status of IP validation. Sleep secure!

Important upgrade notes.

Auto PHP Licenser 2.1 brings lots of other changes, and some of them affect user module. In this case, we recommend developers to update licensing files in their scripts as well. For new scripts, the path is straightforward; integrate licensing engine as per documentation, and you are done. For old scripts, copy main licensing file (overwrite old one) first. Then, merge old and new configuration files. Or generate and use a new one. This is it!

Too lazy to merge configuration file? Submit new support request and we will provide you with detailed instructions. Don’t worry, you will only need to add one line, and (optionally) remove one. Yes, it’s that simple. But what else would you expect from phpmillion?