-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Parse-server does not flag manually created session as "restricted" #5047
Comments
I’m not sure the restricted flag is in used anywhere anymore. Is it something you’d be willing to fix? |
I'm a new guy to parse series and I have not met parse.com before. Maybe it's too hard for me to implement this. So is restricted session obsoleted by parse server? |
I don’t believe it’s in use nor that the restricted flag has any effect. Ensuring it’s set to false should be a good first task, to get to explore the code base. |
Thanks for replying. I will avoid using this. |
There should be no issue with those sessions either. You don’t need to avoid them. |
Issue Description
Parse server did not created a restricted session as described on https://docs.parseplatform.org/rest/guide/#creating-sessions and https://docs.parseplatform.org/rest/guide/#session-properties
Steps to reproduce
Expected Results
A session instance with restricted field set to true is created.
Actual Outcome
A session instance with restricted field set to false is created.
Environment Setup
Server
Database
Logs/Trace
The text was updated successfully, but these errors were encountered: