Skip to content

feat: Allow logout with invalid session token #1803

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 18 commits into
base: alpha
Choose a base branch
from

Conversation

dblythy
Copy link
Member

@dblythy dblythy commented Mar 2, 2023

Pull Request

Issue

Currently, if trying to logout with an invalid session token, you will need to catch the error, and call logout again. It can be a bit tedious.

Closes: #307

Approach

Improves clearing session by allowing Parse.User.logOut({ clearSession: true }), which resolves even if invalid session token is returned.

Tasks

  • Add tests

@parse-github-assistant
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title feat: allow logout with invalid session token feat: Allow logout with invalid session token Mar 2, 2023
@parse-github-assistant
Copy link

Thanks for opening this pull request!

@codecov
Copy link

codecov bot commented Mar 2, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (d098c00) to head (f275357).

Additional details and impacted files
@@            Coverage Diff            @@
##             alpha     #1803   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           64        64           
  Lines         6238      6244    +6     
  Branches      1450      1467   +17     
=========================================
+ Hits          6238      6244    +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mtrezza
Copy link
Member

mtrezza commented Mar 2, 2023

Currently, if trying to logout with an invalid session token, you will need to catch the error, and call logout again.

What would be the difference between the first and second logout request? What makes the first fail and the second succeed?

@mtrezza
Copy link
Member

mtrezza commented Jul 23, 2023

@dblythy Friendly ping regarding the previous question. If the 1st logout attempt fails, why does the 2nd attempt (after catching the error) succeed?

@dplewis
Copy link
Member

dplewis commented Sep 3, 2023

@dblythy We should add this to the server side like parse-community/parse-server#8722 so that it can work for all SDK's

@mtrezza I have no idea why there is a need to call Parse.User.logOut twice when there is a invalid session error to log out. I've been running into this issue a lot while fixing sessionToken invalid issues.

@mtrezza
Copy link
Member

mtrezza commented Sep 3, 2023

Could you please open a separate issue for this?

@dblythy
Copy link
Member Author

dblythy commented Sep 3, 2023

@dplewis see parse-community/parse-server#7277 (comment)

@kishanio
Copy link

are we still tracking this?

@dplewis
Copy link
Member

dplewis commented Apr 2, 2025

@dblythy Nice job! Can you fix the merge conflicts?

@dplewis
Copy link
Member

dplewis commented Apr 16, 2025

@dblythy @mtrezza This is ready to merge

@dplewis dplewis requested a review from a team April 17, 2025 16:25
@@ -812,11 +812,13 @@ class ParseUser<T extends Attributes = Attributes> extends ParseObject<T> {
* <code>current</code> will return <code>null</code>.
*
* @param {object} options
* @param {boolean} [options.clearSession] If true, the session token will be
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this needs a better explanation. It's now a rather technical description but not so clear what the purpose of the option is and why / when one should use it.

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.

Improving Invalid Session Handling
4 participants