Bug #37003
Set user permissions correctly when selecting the location for the user's home directory
Description
When creating a user jmaloney, and selecting a location for home directory /mnt/tank/home the initial permissions for /mnt/tank/home/jmaloney are set to root:wheel. This should be jmaloney:jmaloney. This affects samba homes share functionality until the correct permissions for the user folder are set.
Associated revisions
History
#1
Updated by Joe Maloney almost 3 years ago
- File debug-fn02-20180707150641.txz added
- Private changed from No to Yes
#2
Updated by Dru Lavigne almost 3 years ago
- Assignee changed from Release Council to Anonymous
- Target version changed from Backlog to 11.2-RC2
#3
Updated by Joe Maloney almost 3 years ago
Just adding a note this is not what I thought it was. When adding a user the permissions are fine when setting the home directory. It is when a smb home share is create with the "use as home share" checkbox that all of the user folders ownerships are changed to root:wheel.
#4 Updated by Anonymous almost 3 years ago
- Assignee changed from Anonymous to William Grzybowski
#5 Updated by Anonymous almost 3 years ago Private
Is this something that should be done by the UI or something that the middleware should handle automatically? What do you think William?
#6
Updated by William Grzybowski over 2 years ago
- Category changed from GUI (new) to Middleware
- Assignee changed from William Grzybowski to Brandon Schneider
- Target version changed from 11.2-RC2 to 11.2-BETA2
Can you investigate this please, Brandon?
#8
Updated by Brandon Schneider over 2 years ago
- Status changed from Unscreened to Not Started
#9
Updated by William Grzybowski over 2 years ago
- Assignee changed from Brandon Schneider to Waqar Ahmed
- Severity changed from New to Medium
Waqar, could you please investigate this one?
#10
Updated by Waqar Ahmed over 2 years ago
- Status changed from Not Started to In Progress
#11
Updated by Waqar Ahmed over 2 years ago
Hello. So when a new share is created in the new UI. It automatically sends the default_permissions value as True in new UI when making a call to api v1, which shouldn't happen. This needs to be taken care of on the new UI side. The behavior described in the ticket is not valid for legacy UI. Please let me know if I got this wrong. Thank you
#12
Updated by Bug Clerk over 2 years ago
- Status changed from In Progress to Ready for Testing
#13
Updated by Dru Lavigne over 2 years ago
- File deleted (
debug-fn02-20180707150641.txz)
#14
Updated by Dru Lavigne over 2 years ago
- Subject changed from When selecting a home directory for a user permissions are set incorrectly to Set user permissions correctly when selecting the location for the user's home directory
- Needs Doc changed from Yes to No
- Needs Merging changed from Yes to No
#15
Updated by Dru Lavigne over 2 years ago
- Private changed from Yes to No
#16
Updated by Joe Maloney over 2 years ago
- File Screenshot_20180720_120222.png Screenshot_20180720_120222.png added
- Status changed from Ready for Testing to Passed Testing
This works now.
#17
Updated by Dru Lavigne over 2 years ago
- Status changed from Passed Testing to Done
- Needs QA changed from Yes to No