stock the application with keys or tokens from the inventory tab

Submitted by AviationTechnologies on Sat, 04/02/2011 - 04:03

The license constructor I will be using is the following
License(java.lang.String name, java.lang.String uniqueAppIdentifier, Activity mainActivity)

The name points to the MyApplicense.dat where I will store the license, and the uniqueAppIdentifier is my unique identifier a sequence of 8-32 alpha-numeric characters.

1) The uniqueAppIdentifier will be the same for all users or is it related with the tokens/keys?

2) From what I understand no user interaction is required. The fetch method will automatically return a valid licence for each user who has purchased the application based on "the device unique id"?

3) When I uploaded the free version of the application I was informed that for the paid application I will have to stock the application with keys or tokens from the inventory tab. Could you please provide some further information regarding the tokens/keys?

‹ SlideLock Key vs new phone Any sample application available with working slidelock implementation? ›
Submitted by SlideME on Tue, 04/05/2011 - 18:33.

Inventory & Slidelock

uniqueAppIdentifier is an unique "sequence of 8-32 alpha-numeric characters" that represents each application published on SlideME. You as the developer have the option to choose such a key for your applications; to guarantee it's uniqueness, the back-end validates against the data base.
This key (also called the "SlideLock Key") is only useful when you integrate the SlideLock DRM module within your application - meaning that you will only need such a key when you decide to protect your app from being forwarded.

Tokens OR Keys - you can either opt for Tokens or for Keys, and not for both. They are needed by the system to materialize transactions and inventory.

You are being sent notifications when a sale occurs. Also the end-user receives a similar notification within their purchase receipt that includes your key (you uploaded) or token that was generated for you by the system.

This token/key can be used by your support department and the end-user to match existing transactions in our back-end without our direct involvement.

More into it, you can use the keys to develop your own licensing mechanism, as there is also a configurable post-back API coming for your use.

The only difference between tokens and keys is, if you opt-in for Tokens, we will generate them for you upon your instruction, if you go in for Keys, you will upload them yourself. This may be good in case you have specialized deliverable activation mechanisms which require proprietary keys - like serial numbers, for example.

SlideLock doesn't use these Tokens/Keys, since if you opt for this alternative and proprietary verification mechanism you have the full control of the implementation. SlideLock uses your "SlideLock Key"/uniqueAppIdentifier and device unique identifier to look-up for the transaction in the database, in a secure fashion.