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-plugins fusiondirectory-plugins
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 65
    • Issues 65
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectory-pluginsfusiondirectory-plugins
  • Issues
  • #5909
Something went wrong while setting issue due date.
Closed
Open
Issue created 6 years ago by agallavardin@agallavardinReporter
  • New related issue

  • New related issue

plugin sinaps : check if there is only one SINAPS UUID in ldap leaf of a user

Closed

plugin sinaps : check if there is only one SINAPS UUID in ldap leaf of a user

Requirements

Descriptive title for this enhancement

there is only one or none SINAPS ID in supannRefId

Actual behavior

du to some replication task or bad manipulation, we ( in our system) have got 2 sinaps Id for one user

Expected behavior

A check should be done . If more than one sinaps id is detected an error should occurs ( otherwise SINAPS didn't syunc anything)

Benefits

more coherence

    Tasks

    0

    No tasks are currently assigned. Use tasks to break down this issue into smaller parts.

    Linked items
    0

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

    Activity


    • Côme Chilliet assigned to @MCMic 6 years ago

      assigned to @MCMic

    • bmortier added plugin-sinaps label 6 years ago

      added plugin-sinaps label

    • bmortier
      bmortier @bmortier · 6 years ago
      Maintainer

      hello @gallak,

      work is under way on #5919 (closed)

      supAnn 2009 was not very clear about that

      Cheers

    • bmortier added 5m of time spent at 2019-02-12 6 years ago

      added 5m of time spent at 2019-02-12

    • bmortier added PJ1803-0195 label 6 years ago

      added PJ1803-0195 label

    • Côme Chilliet
      Côme Chilliet @cchilliet · 6 years ago
      Reporter

      #5919 (closed) is about supannRefId value unicity inside the LDAP, this is not the same thing.

      Here, the idea would be to forbid having two values with the same label in supannRefId. Maybe we should ask the SupAnn group about that? (And we need to answer this both for users and structures)

    • bmortier changed milestone to %FusionDirectory 1.3.1 6 years ago

      changed milestone to %FusionDirectory 1.3.1

    • Côme Chilliet
      Côme Chilliet @cchilliet · 6 years ago
      Reporter

      I asked the SupAnn group and they confirmed that there is no unicity constraint on the label in supannRefId.

      So, if we add this, I guess it should be in the SINAPS sync code, not as a general constraint in FD.

    • Côme Chilliet added 15m of time spent at 2019-03-25 6 years ago

      added 15m of time spent at 2019-03-25

    • bmortier changed milestone to %FusionDirectory 1.3.2 6 years ago

      changed milestone to %FusionDirectory 1.3.2

    • bmortier closed 5 years ago

      closed

    • Côme Chilliet removed milestone %FusionDirectory 1.3.2 4 years ago

      removed milestone %FusionDirectory 1.3.2

    Please register or sign in to reply
    Assignee
    Côme Chilliet's avatar
    Côme Chilliet
    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