+3 votes
by
Hello, are developing a client server application. There is a need to identify the user's device.
Was able to find several articles on the subject, but they are all old...
What is now the most current version, and most importantly, correct?
Thank you in advance.

5 Answers

0 votes
by
Android UUID you need. This is a helper classes that will allow you to generate themselves on the basis of the Mac, imei, sn devices (but the implementation you should consider, because for example the tablets do not always have the imei). In General dig/search for the UUID in the direction.
0 votes
by
Google Analytic'is a tricky customer ID, which is most likely associated with the user account in the market.
0 votes
by
You can get AndroidId: Settings.Secure.getString(context.getContentResolver(), Settings.Secure.ANDROID_ID);
However there is a caveat:
A 64-bit number (as a hex string) that is randomly generated when the user first sets up the device and should remain constant for the lifetime of the user's device. The value may change if a factory reset is performed on the device.
I.e. if a user do a hard reset, this value may change.
0 votes
by
I don't know "the correct version"... let me know how I did...

On the server to spin up a socket server and client socket-client. Cling and give the username, password,...
Login and password client Vodytsya on the phone once and stored it for later authorizations...
by
sitev_ru but on the device the password will be stored?
by
"in your case, you can pass the username and password to another person"... And if you do not tell the password? The administrator enters a password, and subsequent automatically logs in... is that okay?
by
The fact that in your case you can pass the username and password to another person, he will introduce it on your device and everything will work. And I need to this was not, this requires some kind of ID.
+1 vote
by
Keep Hesperos user in my database and on the device. Read about hashing (hashing), salt (key salt), KDF
Keep the username and password of the user on the device is not secure - anyone who has received access to the device, if desired, will be able to get them out and to access user data in your service.
UPDATE: actually you need to store a hash of the user password hash
...