There is a website with a lot of users. In order to use the private pages the user has to login with username and password.
Now I'm working on a android app that displays content from the website via an API in a native way, no WebView or similar. The workflow would be the following:
Now I'm searching for a best practice solve for this. I don't want my sessionkeys to be simply hijack-able and I want to be sure that the sessionkey realy belongs to this user. As private data can be seen/modified via the app, privacy is important.
I took a look at oAuth but this isn't what I need I think because I need a consumer key and consumer secret that is unique for every user and I can't integrate this into the app. I don't want to have a new window/browser for entering username+password and handle the response via a callback like oAuth is doing.
Any hints on this?
Thanks a lot!
For a good starting point on http authentication best practices, have a look at this article:
"Principles for Standardized REST Authentication".
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With