'What is the recommended way to limit usage of my /sign_up API to my own mobile client?
I'm already protecting my logged-in (HTTP) APIs behind a user pool/JWT authorization. I'd also like to protect my /sign_up endpoint to avoid it being abused (e.g. to create extra load on the server or cause lots of SMSs/emails to be sent). What's the right way to do that for an HTTP API? IAM with credentials embedded in the mobile app?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|
