Skip to content
GitLab
  • Menu
Projects Groups 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
    • Contributors
    • Graph
    • Compare
  • Issues 34
    • Issues 34
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #3250
Closed
Open
Created Aug 06, 2014 by Côme Chilliet@cchillietReporter

unique is checked only in the object base

I guess it should be LDAP tree wide, right? Meaning if a field is set to unique, it can't have the same value for two object, even if they are not in the same branch. Right now it's not the case.

(from redmine: issue id 3250, created on 2014-08-06, closed on 2015-05-26)

  • Relations:
    • copied_to #1955 (closed)
  • Changesets:
    • Revision 0cdad396 by Côme Chilliet on 2014-08-13T18:52:57.000Z:
Fixes #3250 Using 'whole' unicity for users
  • Uploads:
    • 0001-Fixes-3250-Using-whole-unicity-for-users.patch
Assignee
Assign to
Time tracking