To better secure OAuth 2.0 we implemented IP
Restrictions.
This restrictions 'white list' IP Addresses for a given client
Key/Secret.
We block requests to FatSecret API for a Key/Secret if the
source IP is not white listed.Before releasing IP ranges we
allowed only 15 specific IP addressesThe new 'ranges' allows
users to white list up to 15 ranges of IP addresses.
Example: 0.0.0.0/0 => is a range that allows any IPV4
https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing
For Mobile apps we would recommend using an API proxy server to
avoid Mobile Apps communicating directly with FatSecret APIs.
This proxy should be responsible for:
- Manage the validity / renewal of
your OAuth 2.0 access tokens
- Forward any FatSecret related
requests to FatSecret APIs
We would like to ask you to avoid having your
client’s credentials part of your Mobile App source code /
configuration.
For further technical assistance, please
consult with our dedicated group
forum.
Kind regards,
The FatSecret Platform API Team
--
You received this message because you are subscribed to the Google Groups "FatSecret Platform API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fatsecret-platfor...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fatsecret-platform-api/7252c206-815e-49f0-9a6a-57fc50c45ca1n%40googlegroups.com.
Our Mission is to Enhance the Lives of Billions of users through Profound Technology Solutions.
Since 2003 | CMMI 5 | ISO 27001 | 1000+ Professionals | Top Open Source Agency | Partner: MS Gold, SAP, Google Agency | USA | UK | SNG | SA | India | CISin.com | Linkedin | Coffee-Break | Using e-Signatures?
DISCLAIMER: This message and attachments contains Confidential Proprietary Material & Information and are intended only for the intended recipient(s). If you are not the one, you should delete it immediately to avoid copyright issues.