Multi user switching for quick permisions testing

[JasCodes]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

Even if I try to open another tab, can't have more then one user session.

Feature / Enhancement Description

• Allows to login multiple users.
• Allow to logout all users with single click.
• Easy switching between logged in users.

Example Use Case

Testing permissions

Alternatives / Workarounds

3rd Party References

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

[JasCodes]

@mtrezza feedback please

[davimacedo]

Have you tried the Browser As User option?

[JasCodes]

As, but it doesn't remember more than one user. And its very cumbersome to switch between multiple users.

[davimacedo]

I understand your issue, but I am not sure how the UI would work for what you want. Any suggestion? Maybe can you send a mockup?

[JasCodes]

We can probably design a bit better. Also when you refresh the dashboard it auto resets use the master key all the states should be peristed.

@davimacedo Also I am able to edit CLP from the regular users, and thinking from behind the scene dashboard is using master key. Am I right or as I am new to parse, I am getting security wrong?

[davimacedo]

Yes. You are right. Parse Dashboard uses the master key. The idea of browse as other multiple users makes sense to me. Would you be willed to send a PR?

[mtrezza]

I think that would certainly be a great further development of the Browse-as-user feature. Excited to see your PR!

[JasCodes]

@mtrezza For sure, but I am really new to parse and unfamiliar to the codebase. Though I will love to be a regular code contributor as started using it with two commercial projects. And its always good to give back. Can somebody from the community who knows the codebase do a quick call with me? Is that possible? Are there any web meetups etc?

[mtrezza]

What you could do is take a look at #1750 that added the feature. The code and the discussion thread should give you an idea of how this feature came to be. Then you could make a suggestion on how you'd extend that and get community feedback.