05-15-2013 10:15 AM
Our apps use dynamic licensing, and recently we had issues with our licensing system and decided to change it. As a part of the change, we had to change both the URL and the licensing key. We thought it would be a simple migration, but on release we found that:
1. The existing users who are upgrading are receiving the same license key that was generated when they purchased the license. The app world licensing system does not connect to our new licensing server to generate the keys. The license key seems to be cached alongwith the purchase information.
2. When the existing users switch devices, the app world server connects to the "OLD" licensing server and not the new one. This means that even the license URL is cached alongwith the purchase information.
Does anyone know how to solve this issue?
05-15-2013 10:54 AM
There are lot of issues with this:
1. If our apps get pirated as the license algo becomes known, we cannot change the license key algorithm without affecting the existing users upgrading to the new version.
2. It is not possible to change the licensing URL without affecting the existing users who try to change their devices. For developers using third party licensing systems like licmax, they would be locked in for life with it and it would be the end if the licensing system goes down.
3. If a app world server is not able to get a key from our licensing system for some user during the purchase, it seems to store NULL as the key. And then it always sends the NULL key even if the user deletes and reinstalls the application. Thus the user is never able to install / register the app.
Is there some way we can force the app world server to connect to our licensing server everytime a user downloads the app?