On my mobile app, I'd like to send login and password to the server. Please correct me where I'm wrong, or please tell me how I can improve on this?
We get login/password and authenticate by checking hash of password on the server- we send as response to this some random "session" key (string of random characters?) to the client - later - this is supplied with every request to the server for any other kind of REST request? How do you fit this session key into the REST API without breaking the REST style? i.e., let's say I want to get a list of customers: http://example.com/rest/v1/Customers?session=lksdfkjhsfkjdskfds
--> is this OK?
I feel it's necessary to supply user login direct from my own site AND supply the ability to login by existing google account for example. How do you adapt the login to a REST API with different types of login? What is the common ground between a site supplied user/login vs the google user's API so that the 2 may be used together? The example code I've seen for the google users API abstracts away so much that I don't really understand how it works - you get a user, if it's NULL, you're redirected to a google sign-in. If not, you have your user, then I guess there's some key in the user object that you use as your session key?
Many thanks for any help! :o)