You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the registry server, we are following a token based Authentication, in which if the token is valid and belongs to a particular user in the database, we allow the user to access the API atleast.
But, it has it's downsides as well. For example, if a person has the valid token, they can send in request from any client and if the data is correct then API will perform it's task accordingly.
We can discuss the better approaches to perform authentication in this issue.
Cargo does it the same way. The token cannot be guessed and should obviously not be shared by the user. It also has a limited lifetime. There I'd say that it does the job for now.
In the registry server, we are following a token based Authentication, in which if the token is valid and belongs to a particular user in the database, we allow the user to access the API atleast.
But, it has it's downsides as well. For example, if a person has the valid token, they can send in request from any client and if the data is correct then API will perform it's task accordingly.
We can discuss the better approaches to perform authentication in this issue.
cc: @henilp105 @minhqdao @perazz
The text was updated successfully, but these errors were encountered: