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

Permission error validating a draft request #19

Open
victor-champonnois opened this issue Oct 6, 2022 · 2 comments
Open

Permission error validating a draft request #19

victor-champonnois opened this issue Oct 6, 2022 · 2 comments
Labels
bug no stale Use this label to prevent the automated stale action from closing this PR/Issue.

Comments

@victor-champonnois
Copy link
Member

Error happened when testing beesdoo_base but was also found in a DB with cooperator and without beesdoo_base.
beescoop/Obeesdoo#384

  • Testing beesdoo_base split on lenid.test.coopiteasy.
  • Creation of a user who has only the right to use cooperative management and accounting (
  • login with this user
  • go to cooperators menu and validate a draft request (to male the whole process of creating a new coop and his eaters). I've - got this error message:" Désolé, vous n’êtes pas autorisé à modifier ce document. Seuls les utilisateurs avec les niveaux d'accès suivants sont actuellement autorisés à faire cela: - Administration/Access Rights"
  • to go on with the test, I add this user rights to my user
  • I retry, this error occurs:
    "Désolé, vous n'êtes pas autorisé à créer ce type de document. Seuls les utilisateurs avec les niveaux d'accès suivants sont actuellement autorisés à faire cela: - Other Extra Rights/Accounting / Payments

@robinkeunen said:
cf beescoop/Obeesdoo#427

@victor-champonnois
Copy link
Member Author

Note : after retesting on lenid.test, I can validate the request having only user rights on Cooperative. This seems to be the inverse of the bug stated above (too much permission)

@github-actions
Copy link

github-actions bot commented Apr 9, 2023

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Apr 9, 2023
@robinkeunen robinkeunen added no stale Use this label to prevent the automated stale action from closing this PR/Issue. and removed stale PR/Issue without recent activity, it'll be soon closed automatically. labels Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug no stale Use this label to prevent the automated stale action from closing this PR/Issue.
Projects
None yet
Development

No branches or pull requests

2 participants