Skip to content

Conversation

flovilmart
Copy link
Contributor

@flovilmart flovilmart commented Jun 26, 2016

fixes #1605

Originally, an invalid session token would be let go as a 'nobody' auth, this PR enforces that when an invalid session token is passed, the response should be an error.

@nlutsenko
Copy link
Contributor

LGTM

@flovilmart
Copy link
Contributor Author

let's wait for travis :P

@nlutsenko
Copy link
Contributor

Absolutely! It looks like a good change though.
Please wait for Travis before merging and if it fails - let's discuss this.

@flovilmart
Copy link
Contributor Author

Need to cleanup the error logging I just realized also

@ghost
Copy link

ghost commented Jun 26, 2016

@flovilmart updated the pull request.

- The tests were failin when run in sequence as we called done() before the JSSDK had a chance to register the session token, therefore having a proper logout call in afterEach
@ghost
Copy link

ghost commented Jun 26, 2016

@flovilmart updated the pull request.

1 similar comment
@ghost
Copy link

ghost commented Jun 26, 2016

@flovilmart updated the pull request.

@flovilmart
Copy link
Contributor Author

Stupid test failures... Found the root cause, Parse.User.logOut in afterEach calls were no-ops as we aborted with done before the signup/login call was complete...

@flovilmart
Copy link
Contributor Author

@nlutsenko all good there after the test nits?

@flovilmart flovilmart merged commit 147b493 into master Jun 27, 2016
@flovilmart flovilmart deleted the fix-1605 branch June 27, 2016 03:20
@flovilmart flovilmart mentioned this pull request Jun 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Queries never fail with 'InvalidSessionToken' error when user is logged with legacy session token

2 participants