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
  • #1636
Something went wrong while setting issue due date.
Closed
Open
Issue created 12 years ago by bmortier@bmortierMaintainer
  • New related issue

  • New related issue

Same UID in differents LDAP branches - Issues with FD

Closed

Same UID in differents LDAP branches - Issues with FD

Considering the following scenario :

  • Creation of two departments : team_1 and team_2
  • On first department, creation of a user_1 uid ==> OK
  • On second department, creation of a user_1 uid => OK

In that case, we have twice the same UID created without any conflict detection. That implies the following question / issues :

  • How the user_1 from team_1 and the user_1 form team_2 can login in the FD interface independently for example change their password ?
  • Same question for any external application

As a conclusion shouldn't we have a unicity constraint on the UID in order to avoid such issues ?

(from redmine: issue id 1636, created on 2012-12-02, closed on 2013-04-05)

  • Changesets:
    • Revision 3dcc5d26 by Côme Chilliet on 2013-01-09T16:34:33.000Z:
Fixes: #1636 Fixed bug when several check fails
  • Custom Fields:
    • Bug in version: 1.0.4
  • Uploads:
    • 0001-Fixes-1636-Fixed-bug-when-several-check-fails.patch
An error occurred while loading designs. Please try again.

Tasks

0
Cannot read properties of undefined (reading 'workItem')

Linked items
0

Link issues together to show that they're related. Learn more.

Activity


  • bmortier
    bmortier @bmortier · 12 years ago
    Author Maintainer

    I can't reproduce the problem. I have another one: I created team_1 and team_2, and a user with login user_1 in team_1. I go into team_2, attempt to create a user with login user_1, it says I can't. I cancel, I go look into team_1, I come back into team_2, retry the same creation, and userManagement go into an infinite loop in handlePasswordQueue…

    (from redmine: written on 2013-01-09)

    By Côme Chilliet on 2017-09-02T14:52:39 (imported from GitLab)

  • bmortier
    bmortier @bmortier · 12 years ago
    Author Maintainer

    This fixes the bug I encountered. Regarding ptitoliv request, it appears to me it's already like this as FD is not letting me setting the same uid in two different departments.

    (from redmine: written on 2013-01-09)

    By Côme Chilliet on 2017-09-02T14:52:39 (imported from GitLab)

  • bmortier
    bmortier @bmortier · 12 years ago
    Author Maintainer

    Close issue

    (from redmine: written on 2013-04-05)

    By bmortier on 2017-09-02T14:52:39 (imported from GitLab)

  • bmortier closed 7 years ago

    closed

    By bmortier on 2017-09-02T14:52:39 (imported from GitLab)

  • bmortier added Fixed PJ1802-0188 fusiondirectory-core and removed Bugs labels 6 years ago

    added Fixed PJ1802-0188 fusiondirectory-core and removed Bugs labels

    By bmortier on 2019-01-24T16:23:49 (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
No estimate or time spent
Confidentiality
Not confidential
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
0
0 Participants
Reference:

Menu

Explore Projects Groups Topics Snippets