CODEWITHSUNDEEP
securitysame-origin-policywebsecurityclient-side-attacks
john bowlee
john bowlee

Reputation: 185

Ways to secure API that do not require authentication, to be called only from one pre-defined consumer

I have currently developed a backend app that has some important functionalities. I want to consume my backend endpoints from my frontend but I want to be sure that only my fronted calls the backend endpoint and no other. Currently anyone that access my web-app can take advantage of the functionalities (I do not require any user registration or authentication).

How can I be safe that my backend is not being called form other possible malicious attackers that may try to steal the functionalities of my backend?

I have read some other posts regarding solutions how to secure a backend app that do not require user authentication but none has a precise and secure way for that. Some say enabling CORS but during my experience I can say that CORS can be manipulated easily with the help of a simple browser plugin. (not speaking about mobile apps that do not consider it at all)

I would really appreciate if I would have some opinions in case of a web-frontend-app, mobile app and other backend systems that would try to call my API and how can I stop them.

Upvotes: 2

Views: 3782

Answers (1)

WoJ
WoJ

Reputation: 30044

Typical front-end authentication would be best (OpenID, ...).

If you want something different, you could check on your backend whether a specific header with a specific token is sent in the query. If it is not then you send back a 401 HTTP code.

This requires that your customers somehow get that token (through some registration process, probably) and then keep it long-term (it can be stored in LocalStorage but can be lost when cleaning up the browser)

OWASP Authentication is a good source of information.

Upvotes: 0

Related Questions