Isn’t easier instead of storing a unique token in device registry to store device id (using GetDeviceUniqueId function) in website database and then every time when a request is sent from channel to server to include also device id as parameter?!
Isn’t deleted unique token stored on registry if user reset his device?
Is it possible to display this register page on roku in a category level?
The SDK specifically warns against using the device ID (serial number) as a registration token. If you do this and the user later sells or gives away his device, the new owner will inherit the account of the old user.
Factory reset will remove all contents of all registries. The user would have to relink his device after a factory reset.
I am working on a service with a free trial type system where we want to eliminate the possibility of getting multiple free trials.
Would it be acceptable to log the unique serial # in a separate database but then use the method described in the developer guide for actually authenticating/authorizing the viewer (so a factory reset would disassociate the account from the device, but the device would not be able to generate a second free trial?)
I am working on a service with a free trial type system where we want to eliminate the possibility of getting multiple free trials.
Would it be acceptable to log the unique serial # in a separate database but then use the method described in the developer guide for actually authenticating/authorizing the viewer (so a factory reset would disassociate the account from the device, but the device would not be able to generate a second free trial?)
“360tv” wrote:
Are you going to have the user type in the entire device ID somewhere on your website?
The device ID is available using roDeviceInfo. It’s passed to the website by the player along with the on-screen code and any other pre-registration request info.