2017-12-15 10:18:23 +04:00
2017-12-15 10:01:50 +04:00
2017-12-15 09:45:42 +04:00
2017-12-15 09:45:42 +04:00
2017-12-02 16:02:08 +04:00
2017-11-20 05:49:17 +04:00
2017-12-15 10:18:23 +04:00
2017-12-02 16:13:30 +04:00
2017-12-03 21:06:59 +04:00

Authorization by token's

GitHub Release Build Status Codacy Badge Gitter Badge

Token-based authentication (also known as JSON Web Token authentication) is a new way of handling authentication of users in applications. It is an alternative to session-based authentication.

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

Documentation

License

GNU Banner

GNU GPLv3. Copyright (c) Valentin Popov.

Description
Plugin for Moodle. Token-based authentication.
Readme 225 KiB
Languages
PHP 93.1%
Shell 6.9%