...
Authentification mechanisms
The second part concerns a user and client management system for preventing undesired data manipulations within the internal infrastructure as well as protecting administrative operations.
While it is convinient for end-users to authentificate themselves over a login page applications require an automated process. Hereby, we introduce two authentification machanisms for end-users and applications, such as Flarecast services and algorithms.
| Authentification Mechanism | Used By | Description | Protection Level |
|---|---|---|---|
| Session Login | End-Users | Restricts the permission on specific routes by validating the session ID of a request. If an end-user does not hold an approved session ID he has to authenticate himself over a login page with a username and password. If the login was successful the end-user's session ID becomes active. | Web pages with restricted functions. |
| oAuth2 | Applications | Restricts the permission on specific routes by validating an access token within the request's header. If an application does not hold an active access token it has to request a token from the oAuth2 authentification server. | Restricted REST resources. |
While it is convinient for an end-user to login