diff options
author | Valentin Popov <info@valentineus.link> | 2017-12-15 08:56:14 +0300 |
---|---|---|
committer | Valentin Popov <info@valentineus.link> | 2017-12-15 08:56:14 +0300 |
commit | 10794e59c7197e8e1fb2ce23eb375f30095196db (patch) | |
tree | 89192912940a64cd6bd0b94d44324a29e345a104 | |
parent | c005d271c2b83208a130dc2b5e99efd21ef47e5c (diff) | |
download | auth_token-10794e59c7197e8e1fb2ce23eb375f30095196db.tar.xz auth_token-10794e59c7197e8e1fb2ce23eb375f30095196db.zip |
The file 'README.md' was updated
-rw-r--r-- | README.md | 27 |
1 files changed, 24 insertions, 3 deletions
@@ -1,8 +1,29 @@ -# Authorization by tokens +# Authorization by token's -User authorization module. +Token-based authentication (also known as +[JSON Web Token authentication](https://jwt.io/)) +is a new way of handling authentication of users in applications. +It is an alternative to +[session-based authentication](https://security.stackexchange.com/questions/81756/). -**The plugin is in active development.** +The most notable difference between the session-based and token-based authentication is that former relies heavily on the server. +A record is created for each logged-in user. + +Token-based authentication is stateless - it does not store anything on the server but creates a unique encoded token that gets checked every time a request is made. + +Unlike session-based authentication, a token approach would not associate a user with login information but with a unique token that is used to carry client-host transactions. +Many applications, including Facebook, Google, and GitHub, use the token-based approach. + +## Requirements + +* **PHP**: 5.6.32+; +* **Moodle**: 3.2+; +* **Plug-in**: [tool_managertokens](https://github.com/valentineus/moodle-tool_managertokens); + +## Documentation + +* [Install the plugin](docs/getting-started.md); +* [User's Manual](docs/getting-started.md); ## License |