ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000723ClearOSapp-groups - Group Managerpublic2012-08-24 07:202013-02-16 15:40
Reporterdloper 
Assigned Touser2 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version6.3.0 
Target Version6.4.0 Beta 2Fixed in Version6.4.0 Beta 2 
Summary0000723: app-groups allows group creation with spaces which is disallowed by app-users.
Descriptionapp-users throws 'Disallowed Key Characters.' by design and it is a good thing when a group name contains spaces. The problem can and does occur because the group module allows group names with spaces to be generated in the first place. Group names with spaces can cause some things in Linux to choke and should be avoided.

To fix this issue, disallow the creation of group names that contain spaces in app-groups.
Steps To ReproduceIn app-group, create a group name with a space in it.

Then in app-users, create a user and assign them to that group during the user creation.

NOTE: it is interesting to note that if you assign the user after he has been created in to the group in app-groups, it will allow it.
TagsNo tags attached.
Attached Files

- Relationships
related to 0000932closeduser2 Groups with spaces causes "disallowed key characters" error 
related to 0000933closed Handle groups with spaces 

-  Notes
(0000638)
user2
2013-01-11 20:12

Creating groups with spaces has been disabled in the GUI. The API still accepts groups with spaces since it may run into such scenarios, notably:

- Active Directory Connector
- Samba 4 default groups (e.g. Domain Admins)
(0000639)
user2
2013-01-11 20:12

SVN 5412

- Issue History
Date Modified Username Field Change
2012-08-24 07:20 dloper New Issue
2012-08-24 11:37 user2 Status new => confirmed
2012-08-24 11:37 user2 Target Version => 6.3.0 Updates
2012-10-18 12:29 user2 Target Version 6.3.0 Updates => 6.4.0 Alpha 1
2012-12-06 12:35 user2 Target Version 6.4.0 Alpha 1 => 6.4.0 Beta 1
2012-12-21 09:33 user2 Target Version 6.4.0 Beta 1 => 6.4.0 Beta 2
2013-01-11 19:55 user2 Issue cloned: 0000932
2013-01-11 19:55 user2 Relationship added related to 0000932
2013-01-11 20:12 user2 Note Added: 0000638
2013-01-11 20:12 user2 Status confirmed => resolved
2013-01-11 20:12 user2 Fixed in Version => 6.4.0 Beta 2
2013-01-11 20:12 user2 Resolution open => fixed
2013-01-11 20:12 user2 Assigned To => user2
2013-01-11 20:12 user2 Note Added: 0000639
2013-01-11 20:19 user2 Issue cloned: 0000933
2013-01-11 20:19 user2 Relationship added related to 0000933
2013-02-16 15:40 user2 Status resolved => closed