API Overview
De Wiki1000
(Différences entre les versions)
(→Authentication using session cookies) |
(→Authentication using token) |
||
| Ligne 2 : | Ligne 2 : | ||
==Authentication using token== | ==Authentication using token== | ||
| + | Authentication tokens are managed by administrator using administration interfaces. | ||
| + | A token contains all information relative to a user session, including user, folder and share context identifications. | ||
| + | Tokens are under customer control and could expire or be revoked. | ||
| + | |||
| + | Token must be set in the Authorization http header of requests in bearer format. | ||
| + | |||
==Authentication using session cookies== | ==Authentication using session cookies== | ||
Session cookies are set when a user connects to an Application. | Session cookies are set when a user connects to an Application. | ||
Version du 20 novembre 2020 à 11:31
Sommaire |
Authentication
Authentication using token
Authentication tokens are managed by administrator using administration interfaces. A token contains all information relative to a user session, including user, folder and share context identifications. Tokens are under customer control and could expire or be revoked.
Token must be set in the Authorization http header of requests in bearer format.
Authentication using session cookies
Session cookies are set when a user connects to an Application. To use session cookies your application must act behind a user and manage user connection prior to execute API requests.
See $connect API to manage user connection
