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
  • #2652
Closed
Open
Issue created Aug 21, 2013 by bmortier@bmortierMaintainer

fusiondirectory-insert-schema fails when not cn=config

Maybe add a check to see if ldap is in cn=config, and if not tell the user that he has to manually add the schemas to slapd.conf.

(from redmine: issue id 2652, created on 2013-08-21, closed on 2013-09-25)

  • Changesets:
    • Revision aee38770 by Côme Chilliet on 2013-08-22T09:55:47.000Z:
Fixes: #2652 fusiondirectory-insert-schema fails when not cn=config
  • Revision 44630a69 by Côme Chilliet on 2013-08-22T09:56:09.000Z:
Fixes: #2652 fusiondirectory-insert-schema fails when not cn=config
  • Custom Fields:
    • Bug in version: 1.0.6
  • Uploads:
    • 0001-Fixes-2652-fusiondirectory-insert-schema-fails-when-.patch
Assignee
Assign to
Time tracking