ElecKey Release Notes

Release notes for the official ElecKey releases

PayPal KeyGen with SHA-256 IPN

According to PayPal announcement about 2016 Merchant Security Roadmap, PayPal is in the process of upgrading the protocols used to secure all external connections. These include TLS1.2 and HTTP/1.1 upgrade as well as SSL certificate upgrade using the SHA-256 algorithm and VeriSign's 2048-bit G5 Root Certificate. The PayPal security upgrades will be effective by June 17, 2016.
If you are using the Activation Server from version 2.000 to 2.0.8.41, you need to take action to upgrade the PayPal KeyGen and your systems to support the new security standards. It is important that you finish the upgrade prior to the effective date on June 17, 2016 to avoid any disruption of PayPal IPN interface with the Activation Server.
NOTE: You do not need to take any action if you are using the Activation Server without using the PayPal KeyGen.
Two upgrade options are available as follows.
Option 1: Updating Activation Server Version
  • You must update the Activation Server to version 2.0.8.45 onwards.
  • You must update the existing database (Data.mdb) to the latest database schema.
The following describes the steps involved in updating the Activation Server to support the new security standards, which are included in ElecKey version 2.0.8.45 onwards. Updating the Activation Server to a new version is as simple as when you first deployed the Activation Server to your server. Before you begin, please ensure that you backup all of your Activation Server files including the current database (i.e. the Data.mdb file) as well as the Web.Config and all template files.
To Update Activation Server
First, you must update your ElecKey to the latest release (version 2.0.8.45 onwards). You can run auto update by starting ElecKey Integrator, and click Check for Updates under the About button. ElecKey will download and install the latest version automatically.
Next, Update and replace the new Activation Server files and folders from the following folder to your server.
\ACTIVATIONSERVER\PRECOMPILEDWEB\MANAGER
Finally, upload the backed up Data.mbd, Web.Config, and template files to your server to restore your current database, configuration and templates.
To Update .NET Framework
First, please ensure that your server is set to support .NET Framework 4.5. Since the new Activation Server version adds a new tag to the Web.Config file, you must also copy this tag content shown below and update it to your Web.Config file.
<compilation debug="true" targetFramework="4.5">
  <assemblies>
    <add assembly="Microsoft.VisualC, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
  </assemblies>
</compilation>
To Update Activation Server Database
The new Activation Server version may sometimes updates the database schema with new tables and fields. In this case, you need to perform an additional task to copy and transfer the current data to the new database.
  1. Open the new database file using MS Access.
  2. Remove all Relationships by using the Relationships menu under the Database Tools tab.
  3. From the External Data tab, click the Access icon on the Import pane.
  4. Enter the file name of your current database to the File Name edit box.
  5. Select Link to the data source by creating a linked table. Then, click the OK button. The Link Tables dialog box appears.
  6. Select the available tables: Accounts, Logs, Packages, Permissions, Products, Programs, UpdateLogs, UpgradeLogs, and Upgrades. Then, click the OK button. The linked tables appear in the Tables pane.
  7. Right-click on the linked tables to update to the new database. Click the Copy menu. And, then click the Paste menu. The Paste Table As dialog box appears.
  8. On the Table Name edit box, enter the table name to be updated. Then, select Append Data to Existing Table, and click the OK button.
  9. Repeat step 7 and 8 for all tables.
  10. Login to Activation Manager. Check and ensure that your current data appear in tables correctly under the new database.
  11. Test online activation from your protected application.
  12. Test the PayPal IPN interface with the Activation Server to ensure that it works properly.
Option 2: Recompiling Activation Server
  • You must modify the PayPal KeyGen source code and recompile the Activation Server.
  • There is no need to update the existing database (Data.mdb). You can keep the older database schema.
The following describes the steps involved in recompiling the Activation Server to support the new security standards. To get started, you must have Visual Studio 2012/2013/2015 or later (with C# and ASP.NET) on your machine.
Then, open the solution file below from your ElecKey folder.
\ACTIVATIONSERVER\SERVER\MANAGER.SLN
The Review Project And Solution Changes dialog box will appear. Next, click the OK button.
To Change .NET Target Framework
  1. From Solution Explorer, right-click on the ActSrv project. And, then select Property.
  2. In the Property pane, select the Application tab.
  3. Under the Target framework drop-down list, select .NET Framework 4.5.
  4. From Solution Explorer, right-click on C:\..\Server. And, then select Property Pages.
  5. In the Property Pages dialog box, click the Build tab.
  6. Under the Target framework drop-down list, select .NET Framework 4.5. Then, click the OK button.
  7. From the File menu, click Save All.
To add TLS 1.2 Protocol to PayPal KeyGen
  1. From Solution Explorer, double click on the file PayPal_KeyGen.aspx.cs. The source code will appear in the editor.
  2. Add the code below on the first line of the Page_Load method.
    ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
  3. From the File menu, click Save All.
To Compile Activation Server
  1. From Solution Explorer, right-click on Solution 'Manager' (2 Projects). Then, select Build Solution.
  2. From Solution Explorer, right-click on C:\..\Server. Next, select Publish Web Site, and click the OK button. Then, click the Yes button for confirmation. The compiled version of the Activation Server will be available in \ActivationServer\PrecompiledWeb\Manager.
To Deploy Recompiled Activation Server
First, please ensure that your server is set to support .NET Framework 4.5.
Next, back up the current Bin\App_Web_paypal_keygen.aspx.cdcab7d2.dll file on your server, and replace it with the newly recompiled file from \ActivationServer\PrecompiledWeb\Manager\Bin\ App_Web_paypal_keygen.aspx.cdcab7d2.dll. You may also update the other files that you have edited and recompiled.
Finally, test the PayPal IPN interface with the Activation Server to ensure that it works properly.