[AC-3439] ArrowCloud: session_id mixes up with previous user logged in.

1- Create an App with an ArrowDB project (add two Users user 1 & user 2 in Arrow web portal for simplicity). 2- Create an Node.ACS which also calls the ArrowDB. 3 - The Node.ACS project has a function that creates an ArrowDB Custom Object the User _called createObj_ by passing the session_id. 4- Login as user 1 via the App created (gets session_id, a _direct-API to ArrowDB_) 5- Create an Object owned by user 1 from the App (with the session_id via a Node.ACS call) 6- User 2 logs in and creates another Object (via Node.acs with user 2 session_id) Result (the issue): User 2 creates an Object, however it creates it for User 1 Expected Result: User 2 should create the Object for User 2 (since the session_id is for User 2). This issue has been raised in appcelerator.force.com with Case #: 00007416 Also, the solution was found via Stackoverflow, in which other developers faced this issue as well: [http://stackoverflow.com/questions/27255102/appcelerator-acs-users-login-api-getting-error-code-400-with-message-invalid-r] The solution was clarified here: {quote}for some reason acs-node v0.9.3 appears to be returning the same session ID, even for different users. Some side-effects I've seen include (1) the wrong user attempting to make a change to an object, and (2) objects created by one user are actually owned by the last person who logged in. Making sure acs-node is at v0.9.2 avoids this issue.{quote} Currently, we cannot update our node-acs 0.9.2 to the latest version because of this issue.