Skip to content
GitLab
    • Explore Projects Groups Topics Snippets
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory fusiondirectory
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 39
    • Issues 39
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #4168
Closed
Open
Issue created 9 years ago by bmortier@bmortierMaintainer
  • New related issue

  • New related issue

Underscores in group names not allowed anymore

Closed

Underscores in group names not allowed anymore

Hi,

creating groups with underscores in the name leads to following error: "The field 'Name' contains invalid characters!"

In previous versions, this did not happen, instead there were no upper case letters allowed, which are working now.

So existing groups with underscores in the name will now cause problems during editing, and new ones could not be created with the same naming convention.

Regards

(from redmine: issue id 4168, created on 2015-09-29, closed on 2015-10-06)

  • Relations:
    • relates #4196
  • Changesets:
    • Revision b5f8d27e by Côme Chilliet on 2015-09-29T13:39:40.000Z:
Fixes #4168 Using UidAttribute instead of HostNameAttribute for groups
  • Revision afbe87be by Côme Chilliet on 2015-09-29T13:40:13.000Z:
Fixes #4168 Using UidAttribute instead of HostNameAttribute for groups
  • Revision 131de827 by Côme Chilliet on 2015-09-30T08:23:42.000Z:
Fixes #4168 Using stricter rules for groups even in non-strict mode
  • Revision 631c2318 by Côme Chilliet on 2015-09-30T08:25:52.000Z:
Fixes #4168 Using stricter rules for groups even in non-strict mode
  • Custom Fields:
    • Bug in version: 1.0.9
  • Uploads:
    • 0001-Fixes-4168-Using-UidAttribute-instead-of-HostNameAtt.patch

    Tasks

    ...

    Linked items
    ...

      Related merge requests

      Activity


      • bmortier
        bmortier @bmortier · 9 years ago
        Author Maintainer

        With this patch POSIX groups names will follow the same rules as user logins. We need to decide what to do for groups names (ogroups), because they might have even less strict rules than user logins.

        (from redmine: written on 2015-09-29)

        By Côme Chilliet on 2017-09-02T15:23:49 (imported from GitLab)

      • bmortier
        bmortier @bmortier · 9 years ago
        Author Maintainer

        Pushed this on 1.0.9-fixes and 1.1, for both groups and ogroups.

        (from redmine: written on 2015-09-29)

        By Côme Chilliet on 2017-09-02T15:23:49 (imported from GitLab)

      • bmortier
        bmortier @bmortier · 9 years ago
        Author Maintainer

        Pushed another commit to forbid spaces and uppercase even in non-strict mode.

        (from redmine: written on 2015-09-30)

        By Côme Chilliet on 2017-09-02T15:23:49 (imported from GitLab)

      • bmortier
        bmortier @bmortier · 9 years ago
        Author Maintainer

        To use mixedGroups the change has to be done in admin/groups/class_ogroup.inc as well.

        (from redmine: written on 2015-10-01)

        By mr_claus on 2017-09-02T15:23:49 (imported from GitLab)

      • bmortier
        bmortier @bmortier · 9 years ago
        Author Maintainer

        (Putting back to «to be tested» as the change was already done in ogroups)

        (from redmine: written on 2015-10-05)

        By Côme Chilliet on 2017-09-02T15:23:50 (imported from GitLab)

      • bmortier
        bmortier @bmortier · 9 years ago
        Author Maintainer

        Close issue

        (from redmine: written on 2015-10-06)

        By Jonathan Swaelens on 2017-09-02T15:23:50 (imported from GitLab)

      • bmortier closed 7 years ago

        closed

        By Jonathan Swaelens on 2017-09-02T15:23:50 (imported from GitLab)

      • bmortier added Changed label 6 years ago

        added Changed label

        By bmortier on 2018-10-05T14:54:57 (imported from GitLab)

      Please register or sign in to reply
      Assignee
      bmortier's avatar
      bmortier
      Assign to
      Labels
      0
      None
      0
      None
        Assign labels
      • Manage project labels

      Milestone
      No milestone
      None
      Due date
      None
      None
      None
      Time tracking
      Confidentiality
      Not confidential

      You are going to turn on confidentiality. Only project members with at least the Reporter role, the author, and assignees can view or be notified about this issue.

      Lock issue
      Unlocked
      Participants
      Reference:

      Menu

      Explore Projects Groups Topics Snippets