Common security threats in RESTful web services
Since we have looked at problems in our current code how we will be implementing in some of our endpoints and use authentication middleware, now it is the time to see what the common security threats that we need to consider while building RESTful web services are.
Use of HTTPS
HTTPS is HTTP with SSL. As our data is being transferred the internet, we need to make our connection secure; for that reason, we should use HTTPS. The purpose of is to make sure that the server is who it claims to be and that data is transferred between the client and server with a secure connection in an encrypted form.
If you don't want to buy an SSL certificate as it is costly for you, then can simply go for https://letsencrypt.org/. Let's Encrypt is a free certificate authority. So, you can use it without paying for an SSL certificate.
Securing an API key/token
As our sessions will be based on a token, we need to secure authentication token. There different things...
