Skip to content
GitLab
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 33
    • Issues 33
    • 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
  • #5261
Closed
Open
Issue created Nov 28, 2016 by bmortier@bmortierMaintainer

Allow for manual configuration of LDAP base

In a situation where the looked up LDAP base is cn=example,cn=com, It appears, that it is not possible for the user to change the base to something like ou=fd,cn=example,cn=com.

Having FusionDirectory data in it's own OU with an associated FD user in LDAP would be good security practice (The requester thinks).

(from redmine: issue id 5261, created on 2016-11-28, closed on 2017-02-21)

  • Changesets:
    • Revision 6d924c58 by Côme Chilliet on 2017-02-15T09:58:32.000Z:
Fixes #5261 If base detection fails, fall back to StringAttribute
  • Revision 6e9f4cf3 by Côme Chilliet on 2017-02-21T08:28:12.000Z:
Fixes #5261 Using StringAttribute if LDAP base detection fails
  • Custom Fields:
    • Bug in version: 1.0.19
Assignee
Assign to
Time tracking