-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Self-Service Users is able to reserve all reservable items, not only the ones of his entities. #16322
Comments
All |
Hi, On my side, I can only reserve items that are from the user entity or from a parent entity with the "+child entities" visibility flag active. I think it is the normal behaviour. |
I agree that the behaviour you describe is the normal one. But It's not my case. Then I go to calendar and try ro reserve items : It proposes me Computers of B entity, which is parallel to A entity When I connect to B entity with the same profile, I can see the reservation => normal I'm confused. |
I confirm the issue. The list from the reservation calendar view ( |
Thanks. As I'm in a blocking situation (A whole team may not come to GLPI because of this bug) , I'm volontary to test fixes on my dev GLPI server when you have them. |
Can you test the fix proposed in #16359? |
I confirm that the new src/ReservationItem.php fixes the issue. |
Code of Conduct
Is there an existing issue for this?
Version
10.0.10
Bug description
A Self-Service User can reserve any reservable asset, not only the ones of his entities.
User should be able to reserve assets of the entity his connected on.
Relevant log output
No response
Page URL
No response
Steps To reproduce
1- connect to entity A with a profile able to reserve asset
2- Go to reservations
3- user can reserve asset of any entity, not only the ones of entity A
Your GLPI setup information
Information about system installation & configuration
Server
GLPI constants
Libraries
LDAP directories
SQL replicas
Notifications
Plugins list
Anything else?
No response
The text was updated successfully, but these errors were encountered: