Forum Activity for @nate

nate
@nate
02/04/15 07:41:20PM
917 posts

Proxima Login fail


Proxima

So, I sign up I get a session back I can use it fine.

When I log in later (as I will have to eventually), if the user has any session in the db (expired or not), it does not record a new session in the db. It only updates the existing session with a new expiration time, and returns a new session id to my app. I can ignore this new id but is that how it's suppose to work?



updated by @nate: 02/04/15 08:27:11PM
nate
@nate
02/04/15 07:35:16PM
917 posts

Proxima Login fail


Proxima

What it is doing is updating the existing session with a new expiration time. But it's returning a brand new session_id.
nate
@nate
02/04/15 07:18:48PM
917 posts

Proxima Login fail


Proxima

It 0nly works sometimes.

{"code":200,"text":"OK","note":"session started","data":{"session_id":"70572eefa9709aa68ab0dd2b07b5a74c"}}

------------------------------

cc51c83f8affd1dd2fc022e54ea23d78 2 40 41 1423711072

Seems to work properly only when the table is empty.
updated by @nate: 02/04/15 07:20:18PM
nate
@nate
02/04/15 07:07:54PM
917 posts

Proxima Login fail


Proxima

Note. it's not being recorded but it is returning a session_id. As if it is being recorded.
nate
@nate
02/04/15 07:05:10PM
917 posts

Proxima Login fail


Proxima

Ok so what's going on is, if a user with an existing session logs in the session is not being recorded. If I delete all sessions, I can log in and everything works. I can try to set my expiration date to match yours. Is it 7 exact days?
nate
@nate
02/04/15 06:47:07PM
917 posts

Proxima Login fail


Proxima

I just did another log in, got back a session_id, checked the db and there is no session recorded.

I did this twice with no session recorded now.
updated by @nate: 02/04/15 06:53:14PM
nate
@nate
02/04/15 05:48:12PM
917 posts

Proxima Login fail


Proxima

Quote: cd33784ce52dce710d28bc60056e657e 2 38 39 1423702283

{"session_id":"4476e810c631dece12aa398bd73f7b00"}

Quote: 6ee36a4827fddc202b0cdb654cc023dc 2 39 40 1423702429

{"_id":39,"session_id":"6ee36a4827fddc202b0cdb654cc023dc","location":"http:\/\/n8flex.com\/api\/user\/39"}
nate
@nate
02/04/15 05:44:42PM
917 posts

Proxima Login fail


Proxima

When I create a user, I get the same session_id returned as the session_key recorded. When I later try to log in as an existing user, the session_id returned does not match the session_key in the DB.

Are you saying somehow the data is being read wrong by my app? Only on log in and not when I create a user? I'm logging it as a raw string before I do anything to it. They use the same handler upon return.
nate
@nate
02/04/15 05:18:16PM
917 posts

Proxima Login fail


Proxima

So that we're clear, the error is happening at log in, not at the payment post. The session returned does not match the session recorded.
nate
@nate
02/04/15 05:07:34PM
917 posts

Proxima Login fail


Proxima

Yes, if the user goes to make a payment beyond 6 days the app logs in to have a valid session. For testing, I've changed it to 10 seconds.

I deleted all proxima sessions and these are the only 2 present. The first was a log in attempt by user 38.

Quote: I/PaymentActivity﹕ {"code":200,"text":"OK","note":"session started","data":{"session_id":"4476e810c631dece12aa398bd73f7b00"}}

recorded
Quote: cd33784ce52dce710d28bc60056e657e

On the second one, I created a new user, 39.

Quote: {"code":201,"text":"Created","note":"user created and session started","data":{"_id":39,"session_id":"6ee36a4827fddc202b0cdb654cc023dc","location":"http:\/\/n8flex.com\/api\/user\/39"}}

recorded
Quote: 6ee36a4827fddc202b0cdb654cc023dc

updated by @nate: 02/04/15 05:13:50PM
  66