Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

  •  
     
    story #8208 have nightly LDAP synchro with Active Directory
Actions
Summary
site administrator
have nightly LDAP synchro with Active Directory
People who left the company are desactivated at Tuleap side

Follow-up story #8207:

  • Nighlty synchronization
    • Account update (if user attributes change)
    • Account suspend
      • Only if user is no longer present in AD
      • Fix the bug with all user suspended when using AD
  • Documentation & valid
    • No specific validation tests added there
    • Documentation about LDAP should explain what this daily synchro does
Empty
Empty
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#8208
Manuel Vacelet (vaceletm)
2015-07-29 16:52
2015-07-08 10:12
7901

References
Artifact links
Empty
Referencing story #8208

Artifact Tracker v5

story #8207 use Active Directory as an LDAP directory
epic #8209 LDAP & Authentication
rel #8245 8.5
Referenced by story #8208

Artifact Tracker v5

story #8207 use Active Directory as an LDAP directory
Display settings

Follow-ups

User avatar
Manuel Vacelet (vaceletm)2015-07-29 16:52
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Status changed from Ready (stalled) to Done
  • Category set to
User avatar
dylan bowden (dylan)2015-07-23 11:52
Correction, I missed some attributes for the nightly synchro (mail, cn) but both work out-of-box
User avatar
dylan bowden (dylan)2015-07-23 11:07
  • Nighlty synchronization
    • Account update (if user attributes change)
      • We use the username property as an ID for Active Directory users. Thus if login changes, we are unable to detect it. Given that this is the only attribute which is updated, there is nothing to do.
    • Account suspend
      • Only if user is no longer present in AD
        • Works out of the box
      • Fix the bug with all user suspended when using AD
        • bug seemingly not present with proper set-up
  • Documentation & valid
    • No specific validation tests added there
    • Documentation about LDAP should explain what this daily synchro does