Anonymous | Login | 2024-12-03 10:08 MST |
Main | My View | View Issues | Change Log | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0000102 | ClearOS | app-users - User Manager | public | 2010-06-04 09:42 | 2011-02-02 14:35 | ||||
Reporter | user2 | ||||||||
Assigned To | user2 | ||||||||
Priority | high | Severity | major | Reproducibility | always | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | 5.1 | ||||||||
Target Version | 5.2 | Fixed in Version | 5.2 | ||||||
Summary | 0000102: Disallow duplicate Windows group names | ||||||||
Description | When a new group is created, the system will check for duplicate Linux group names. These group names are mapped into the Samba/Windows world on a 1-to-1 basis. In other words, a Linux group "sales" is mapped to "sales" in Samba/Windows. Some built-in groups have a slightly different mapping, for example: "domain_users" is mapped to "Domain Users" When webconfig performs a check for duplicate group names, it checks the Linux name (e.g. domain_users), but it should also check the Windows mapping. Right now, you can add a group "Domain Users" in webconfig and it will be happily accepted. That... is bad. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Notes | |
(0000171) user2 2010-06-08 21:30 edited on: 2010-08-18 15:14 |
Source Code Changelog --------------------------------------------------- - Added Windows group name (displayName attribute) to LDAP uniqueness check [fixed tracker 0000102] File Changes --------------------------------------------------- U legacy/webconfig/trunk/api/ClearDirectory.class.php |