-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Read Auto Faveo Licenser documentation, explore advanced usage tips, find detailed answers to frequently asked questions, and troubleshoot common issues.
Before you can start protecting your script with Auto Faveo Licenser, it only takes 3 easy steps: adding product, adding client (optional), and adding license itself. For your convenience, all the steps are fully explained below.
The first and most obvious step to maintain a product is to create the product itself. Open the Products » Add New Product tab to create your product. Product name, SKU, and security key fields are mandatory and must be unique (different products with same name and/or SKU and/or security key can't exist), while other fields are optional. The number of products is unlimited.
All previously added products can be edited using the Products » View Products tab. Click desired product name to make any changes needed. Even if license for a particular product is in use, all the details (even product name or SKU) can be modified without affecting existing installations.
Setting product status to Inactive will deactivate all licenses issued for this product. For example, if there are 10 clients with active licenses for particular product, all 10 licenses will not be available to use anymore. This option should only be used if you want to prevent users from using a particular product for some reason.
Once product is created, add a new client. Open the Clients » Add New Client tab to add a client who will use licensed product. All fields are mandatory. Since email address is used to identify client and verify his license, it must be unique (different clients with same email address can't exist). The number of clients is unlimited.
While it's always recommended to create client's profile before issuing a license, there might be a scenario when you don't know client's details (such as name and email) or want to issue anonymous license. In case that happens, just skip this step.
Just like products, existing clients can also be edited using the Clients » View Clients tab. Click desired client name to make any changes needed. Client first and last name can be modified at any time, but modifying licensed email address after license is issued will cause a failure of client's license verification. In order to continue using his license issued under old email address, client will need to update his licensed email address in installed script. Just as you would expect, setting client status to Inactive will deactivate all licenses issued for selected client. For example, if client has 5 separate licenses for 5 different products, all 5 licenses will become inactive.
Finally, it's time to issue a new license. Open the Licenses » Add New License tab to add a new license. When client's details are known, select client and product from the list. In case you don't know client's name and email (so you can't create client's profile), select product from the list and enter unique license code. This way, anyone having this code will be able to activate his copy of protected script.
Only product and client (for personal licenses) or license code (for anonymous licenses) fields are mandatory, while optional fields can be used to bind license to specific IP address and/or domain, limit the number of allowed installations, or even cause license to expire at specific date. More on that below.
If IP address is entered, application will only work on a specific IP address. Once IP is changed, license check will fail. If domain is entered, application will only work on a specific domain. Domain should always be entered as clientdomain.com or clientdomain.com/path (it should never include / symbol at the end). If licensed domain is entered as clientdomain.com, product will work on clientdomain.com and clientdomain.com/any/directory. If licensed domain is entered as clientdomain.com/path, product will only work on clientdomain.com/path. Sure enough, both IP and domain fields can be filled at the same time, so application will only work if IP address matches domain (for example, if IP address 1.1.1.1 and domain clientdomain.com is set, but clientdomain.com actually points to 1.1.1.2, application will not work). It's also possible to add multiple licensed IPs and/or domains by separating them with comma (,) symbol.
An option to always require a domain can also be used; it will block all installation attempts on invalid domains (in other words, installations on http://localhost or http://1.1.1.1 will fail).
If installations limit is set, client will not be able to perform more installations once limit is reached. For example, if current limit is 2 installations, 3rd installation will only work when one of previous installations is deleted using the View Installations tab (the limit is set per license). If installations limit is set, IP address and/or domain fields can be left empty, since client will not be able to perform any more installations anyway (no matter domain and/or IP).
If expiration date is set, application will stop working after this date (expiration date can be updated at any time). Additionally, it's possible to set updates and support expiration dates. If updates and/or support expiration date is set, application will continue working as long as the license is active, but updates and/or support will not be available after this date.
If IP verification is disabled, Auto Faveo Licenser will mark license verification as successful even if user's IP address doesn't match IP used to install protected script. Other verifications (licensed product, installation path, expiration dates, etc.) will be performed as usually. Be aware that disabling IP verification will reduce overall protection for particular installation, so only enable this emergency option if you don't have another choice. But before you do, contact our support team first, so we can provide you with step-by-step instructions on how to protect this particular installation from piracy with the help of other options available in Auto PHP Licenser. Also keep in mind that installations limit might not work when IP verification is disabled.
All issued licenses be edited using the Licenses » View Licenses tab. Click desired license to make any changes needed. If license is in use, be aware that modifying license data might cause license verification to fail. For example, if application is installed on clientdomain.com and licensed domain is changed to clientdomain.com/path, existing installation will stop working. In other hand, license modification is a must when some details (such as client's IP address) was changed, so client can continue using protected script.
For obvious security reasons, licensed product or license owner can not be changed after license is issued. If existing client needs a license for another product, just terminate his existing license (optional) and issue a new one. Setting license status to Inactive will deactivate this license. For example, if client has 3 separate licenses for 3 different products, deactivating one license will prevent client from using a particular product, but allow him using other two products he still has active licenses for.
All installations be edited using the Installations » View Installations tab. Click desired installation to make any changes needed. For security reasons, only installation IP address and status can be modified. An existing installation should only be modified if client's IP address was changed and license verification failed. Otherwise, installation details should never be modified. Deactivating or completely deleting an existing installation will cause license verification to fail and client will need to re-install protected application.
Auto Faveo Licenser allows displaying custom notifications in your application for each event (failed license check, expired license, etc.) and/or sending automated reminder emails about expiring license, updates, and support. Open the Server Notifications » Customize Notifications tab to modify these notifications or the Server Notifications » Customize Emails tab to modify reminder emails. The full list of supported variables is below (all variables are sorted alphabetically):
| Variable Name | Variable Value | Notes |
|---|---|---|
| %CLIENT_EMAIL% | Client's email address | Only available for personal licenses |
| %CLIENT_FNAME% | Client's first name | Only available for personal licenses |
| %CLIENT_LNAME% | Client's last name | Only available for personal licenses |
| %IP_ADDRESS% | IP address of user's machine | Not available in reminder emails |
| %LICENSE_CANCEL_DATE% | License cancellation date | Only available for cancelled licenses |
| %LICENSE_CODE% | License code | Only available for anonymous licenses |
| %LICENSE_EXPIRE_DATE% | License expiration date | Only available for time-expiring licenses |
| %LICENSE_LIMIT% | Number of allowed installations | Only available for licenses with installations limit |
| %LICENSE_SUPPORT_DATE% | Support expiration date | Only available for support-expiring licenses |
| %LICENSE_UPDATES_DATE% | Updates expiration date | Only available for updates-expiring licenses |
| %PRODUCT_DESCRIPTION% | Product description | Not available for 'Invalid License' notification |
| %PRODUCT_ID% | Internal product ID | Not recommended to display for security reasons. Not available for 'Invalid License' notification |
| %PRODUCT_TITLE% | Product title | Not available for 'Invalid License' notification |
| %PRODUCT_URL_DOWNLOAD% | Product download URL | Not available for 'Invalid License' notification |
| %PRODUCT_URL_HOMEPAGE% | Product homepage URL | Not available for 'Invalid License' notification |
| %PRODUCT_VERSION% | Current product version | Not available for 'Invalid License' notification |
| %ROOT_URL% | URL where application is (being) installed | Not available in reminder emails |