parse-community / parse-community/parse-server
setPassword expires current session even when revokeSessionOnPasswordReset=false
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest version of Parse Server.
Issue Description
We are using function setPassword to change password in the cloud code function. However, even when we have revokeSessionOnPasswordReset set to false, the current session expires (but not other sessions of the user - that is correct).
Steps to reproduce
Use setPassword function on ParseUser object in cloudCode function
Actual Outcome
The current session expires (parse server returns "Invalid session"
Expected Outcome
The session should be valid
Server
- Parse Server version: 4.5.0
- Operating system: docker image
- Local or remote host: Digital Ocean kubernetess
Database
- System (MongoDB or Postgres): Postgres
- Database version: 11
- Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Digital Ocean managed DB
Client
- SDK (iOS, Android, JavaScript, PHP, Unity, etc): Cloud code javascript
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing setPassword in a JavaScript Cloud Code function with revokeSessionOnPasswordReset set to false, then trace the password-reset session handling in Parse Server. Done means the current session remains valid while other sessions continue to be revoked as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100