Skip to content
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

security concern: singleton nature is not documented. #10

Open
markstos opened this issue Apr 1, 2021 · 0 comments · May be fixed by #15
Open

security concern: singleton nature is not documented. #10

markstos opened this issue Apr 1, 2021 · 0 comments · May be fixed by #15

Comments

@markstos
Copy link

markstos commented Apr 1, 2021

In my testing, if two projects are both loaded and use the authorized module, the state is shared between the two projects.

So if one project defines an edit user action and a second project defines an edit user action, the second would overwrite the first.

At a minimum, the documentation should disclaim the singleton behavior and note that it's only intended to be used by project at a time.

markstos added a commit to RideAmigosCorp/authorized that referenced this issue Apr 2, 2021
and how to share state between multiple instances.

Fixes tschaub#10
markstos added a commit to RideAmigosCorp/authorized that referenced this issue Apr 2, 2021
and how to share state between multiple instances.

Fixes tschaub#10
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 a pull request may close this issue.

1 participant