Users signed in using OAuth have only 1 sessionToken per Sign-In #4328

Activity

1. cipiripper commented on Nov 8, 2017

   

   cipiripper

   on Nov 8, 2017

   ContributorAuthor

   More actions

   Okay this as well RestWrite.js:

   // Destroy the sessions in 'Background'
     this.config.database.destroy('_Session', {
       user: {
         __type: 'Pointer',
         className: '_User',
         objectId: this.objectId()
       },
       installationId: this.auth.installationId,
       sessionToken: { '$ne': token },
     });
   

   So when user logs in, all his SessionTokens from this installationId get removed... Why(infinity * ?)
2. flovilmart commented on Nov 8, 2017

   

   flovilmart

   on Nov 8, 2017

   Contributor

   More actions

   this only destroy the session for the this.auth.installationId so should never affect other sessions that were created on other devices.
3. montymxb commented on Nov 8, 2017

   

   montymxb

   on Nov 8, 2017

   Last edited by montymxb

   Contributor

   More actions

   @cipiripper Looking back in the history it looks like this was changed in #4143 to address #2885, as this was a bug and not expected functionality. You can see this is noted in the docs as well. The history there indicates this language was present in the initial commit so it probably was the same for parse.com.
   Disregard for comment below, although the change above was for a bug fix it was not something that should have an impact on this issue.
4. montymxb commented on Nov 8, 2017

   

   montymxb

   on Nov 8, 2017

   Contributor

   More actions

   To agree with @flovilmart this shouldn't cause you a problem as it's just clearing duplicates for multiple sessions with the same installationId. The device and browser session shouldn't conflict with each other in this regard, unless a matching installationId was being set onto the web session for some reason.
5. cipiripper commented on Nov 8, 2017

   

   cipiripper

   on Nov 8, 2017 via email

   ContributorAuthor

   More actions

   Thanks for your feedback guys, I will investigate this some more...

   👍React with 👍1Reacted by Benjamin Friedman Wilson
6. stale commented on Sep 18, 2018

   

   stalebot

   on Sep 18, 2018

   More actions

   This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
7. stale

   added

   wontfix

   on Sep 18, 2018
8. stale

   closed this as completedon Sep 25, 2018