To protect a webservice it's a good option to use
- a login (userid/mail & pw) = every user of your app has to sign on
- strong encryption methods
- additionally parameters like IMEI (if available) or other keys to check if the caller is authorized
- two factor authorization (like login AND additionally send a code to the registered mail address
- tan lists (list is generated when the customer creates an account) which can be stored on the device as a ADDITIONAL check when you need a automatic solution
- check multiple logins (via IP and login tries, block ip's and or users -> send a mail that the user is blocked and some action is needed to activate the accoutn again)
URL:
Use (at least) two URL's:
- one for the login (which is included in the app's code)
- the others are coming from the server after login and are kept in memory
It's all about to store "nothing" in your app and retrieve "everything" from your server