|
|
|
|
|
by bpicolo
1979 days ago
|
|
Giving frontend clients the keys to the castle to send text messages and make calls on your app's behalf seems like a bad time waiting to happen. How are you thinking about the security aspect? I see the word "Security focused", but that doesn't really tell me anything. Kinda the same deal on Stripe - if someone can guess / find out customer identifiers, which is a lot more likely when you're shipping them to frontends to use with your library (XSS...), they can create charges on your behalf? That's definitely a big risk fanout |
|
We handle security in a few ways;
- Clients are initialised with Key & ID - We advocate for keys to not be hardcoded
- The key is used for request encryption and are never sent to the server. Request hashes are also used to make sure Man In the Middle Attacks are avoided
- Custom Auth Tokens can be sent with requests - On the server side we use your provided auth callback to ensure it is valid
What do you think about the steps we take? Tokens are really important because they offer another layer of protection