Timeline for Authentication and authorisation for people with intellectual disabilities
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 17, 2023 at 8:20 | history | edited | Laiv | CC BY-SA 4.0 |
added 82 characters in body
|
| Apr 12, 2023 at 7:41 | history | edited | Laiv | CC BY-SA 4.0 |
deleted 79 characters in body
|
| Apr 12, 2023 at 7:01 | comment | added | Laiv | @KDW I mentioned blockchain and smart contracts in case you need to do some research but, certainly, you can implement the same principles in a traditional (centralized) web system. The takeaway ideas are KYC, auth by consensus and biometrics as MFA. | |
| Apr 12, 2023 at 0:35 | comment | added | user1937198 | @KDW You don't even need blockchains to implement such techniques for a centralized authentication system. Look at how cloud IAM systems handle server authorization in a least privilege model. You have server host accounts which have permissions to generate authorization for container accounts that have permissions to perform the relevant task. | |
| Apr 11, 2023 at 19:29 | comment | added | KDW | The suggestion about blockchain with smart contracts is certainly something to further explore and honestly was not something I already took into consideration. Thanks for pointing it out! | |
| Apr 11, 2023 at 17:56 | comment | added | Greg Burghardt | This answer really addresses the core of the problem. "We are speaking about a group of users who depends (a lot) on someone else, so the security must involve the capacity to trust in that someone else." -- in general, "trust" is the foundation of any security paradigm. This is especially true when the primary benefactor of the system is unable to participate in the authentication/authorization process. Technology alone won't solve this. Other people, polices, and procedures must be involved. Great answer! | |
| Apr 11, 2023 at 14:39 | history | answered | Laiv | CC BY-SA 4.0 |