Timeline for Log off system on all devices
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 10, 2016 at 7:14 | comment | added | Falgantil | Well, you don't. And that's when the user would use the 'Invalidate all tokens'-functionality. | |
| Oct 10, 2016 at 7:10 | comment | added | H. Pauwelyn | What I've expected. But how do you know that the device that will authenticate is always the same with a unique code. I mean what if the token of device A is stolen and the token will be used for authenticate device B? | |
| Oct 10, 2016 at 6:57 | comment | added | Falgantil | Usually every device has a unique token. Otherwise you wouldn't be able to identify devices, and it would make it a lot more insecure to use the same token for all devices. If the token was leaked without your knowledge, someone else could be impersonating you, because you'd only have 1 unique token. | |
| Oct 10, 2016 at 5:51 | comment | added | H. Pauwelyn | I've one more question for you. 1. Has every user a unique token that could used for multiple devices or 2. is that one unique token for each device and a user got multiple unique tokens | |
| Oct 4, 2016 at 18:03 | comment | added | H. Pauwelyn | Sorry but I havn't exlpain that Facebook and Twitter are just some examples. I haven't say that I was asking for a gereral solution. Thanks for answer. | |
| Oct 4, 2016 at 15:37 | vote | accept | H. Pauwelyn | ||
| Oct 4, 2016 at 11:25 | review | First posts | |||
| Oct 14, 2016 at 14:51 | |||||
| Oct 4, 2016 at 11:23 | history | answered | Falgantil | CC BY-SA 3.0 |