Users Authentication


There are four ways to Autenticate user:
- atNone ("AuthType": "atNone")
- atUser ("AuthType": "atUser")
- POST/API/Users/Authwithcookie
- POST/API/Users/Authwithtoken
|
1. atNone ("AuthType": "atNone")
If the Parama AuthType is set to atNone in this case there is no autentification, the user is taken form the connection string in appsettings.json file

2. atUser ("AuthType": "atUser")
If param AuthType is set to atUser in this case at each connection the user and password are send to create connection string.

2.1 Example for Advanced REST client:

Selected Basic authorisation allowes you to send username and password in a request header.
Or you can enter in service HEADER:
authorization: Basic XXXXXXXXXXXX
where XXXXXXXXXXXX is base64 encripted username: password
Or you can use some other authentication method which is allowed by client aplication.
3. POST/API/Users/Authwithcookie
This API generate cookie atCookie ("AuthType": "atCookie") for autorisation in JSON form.
User and password will be send in .json format.
{
"username": "string",
"password": "string"
}



Expiration in minutes is set in param "CookieExpiresMinutes": 2,
4. POST/API/Users/Authwithtoken
This API gnerate token atToken ("AuthType": "atToken",) in JSON form needed for autorisation in each API service call.
{
"username": "string",
"password": "string"
}
User and password will be send in .json format.



Selected Bearer authorization allows to send an authentication token in the authorization header using the 'bearer' method.
Or you can add token in the service HEADER.
authorization: Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Token Expiration in days: "TokenExpiresDays": 1,
Tokens can be in JWT or JSON Web Tokens (https://jwt.io/).