API Overview
De Wiki1000
(Différences entre les versions)
(→Authentication using token) |
(→Authentication) |
||
| Ligne 1 : | Ligne 1 : | ||
=Authentication= | =Authentication= | ||
| + | API accesses must be authentified | ||
| + | |||
| + | There are two ways to manage authentication : | ||
| + | * Token based | ||
| + | * Session based | ||
==Authentication using token== | ==Authentication using token== | ||
| − | |||
A token contains all information relative to a user session, including user, folder and share context identifications. | A token contains all information relative to a user session, including user, folder and share context identifications. | ||
| + | Authentication tokens are managed by administrator using administration interfaces. | ||
Tokens are under customer control and could expire or be revoked. | Tokens are under customer control and could expire or be revoked. | ||
Version du 20 novembre 2020 à 11:40
Sommaire |
Authentication
API accesses must be authentified
There are two ways to manage authentication :
- Token based
- Session based
Authentication using token
A token contains all information relative to a user session, including user, folder and share context identifications. Authentication tokens are managed by administrator using administration interfaces. 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
