Project

General

Profile

Bug #37003

Set user permissions correctly when selecting the location for the user's home directory

Added by Joe Maloney 10 months ago. Updated 9 months ago.

Status:
Done
Priority:
Nice to have
Assignee:
Waqar Ahmed
Category:
Middleware
Target version:
Seen in:
Severity:
Medium
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

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.

Screenshot_20180720_120222.png (244 KB) Screenshot_20180720_120222.png Joe Maloney, 07/20/2018 09:06 AM
22155

Associated revisions

Revision 56fa7e18 (diff)
Added by Waqar Ahmed 9 months ago

Permission bug fixed in smb plugin

When home was set to true when creating a samba share, it used to recursively set each directory in the path's permissions to the parent directory permissions. This commit changes that and when home is true, the permissions of directories beneath it don't change.
Ticket: #37003

History

#1 Updated by Joe Maloney 10 months ago

  • File debug-fn02-20180707150641.txz added
  • Private changed from No to Yes

#2 Updated by Dru Lavigne 10 months ago

  • Assignee changed from Release Council to Erin Clark
  • Target version changed from Backlog to 11.2-RC2

#3 Updated by Joe Maloney 10 months 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 Erin Clark 9 months ago

  • Assignee changed from Erin Clark to William Grzybowski

#6 Updated by William Grzybowski 9 months 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 9 months ago

  • Status changed from Unscreened to Not Started

#9 Updated by William Grzybowski 9 months 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 9 months ago

  • Status changed from Not Started to In Progress

#11 Updated by Waqar Ahmed 9 months 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 9 months ago

  • Status changed from In Progress to Ready for Testing

#13 Updated by Dru Lavigne 9 months ago

  • File deleted (debug-fn02-20180707150641.txz)

#14 Updated by Dru Lavigne 9 months 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 9 months ago

  • Private changed from Yes to No

#16 Updated by Joe Maloney 9 months ago

22155

This works now.

#17 Updated by Dru Lavigne 9 months ago

  • Status changed from Passed Testing to Done
  • Needs QA changed from Yes to No

Also available in: Atom PDF