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

No (obvious) way to select the pool allocation method

In earlier versions, we could set the idAllocationMethod to pool (default being traditional) in the fusiondirectory.conf flat file, and also the min and max uid/gid allowed. Now that all the conf is in LDAP, it looks like there's no way to select the pool allocation method because the following attribute are not defined in LDAP:

fdidAllocationMethod fduidPoolMin fduidPoolMax fdgidPoolMin fdgidPoolMax

There's a fdIdGenerator attribute defined in the schema, which should be usable, but:

  • get_next_id function (in functions.inc) still tries to read idAllocationMethod, which doesn't exists
  • this fdIdGenerator attribute can be set in the general config with a free field. It should be changed to a drop-down list with only valid allocation methods (pool or traditional), so it's more obvious how to change this setting
  • the min and max attrs are still not available, so the default of 10000 and 40000 (hardcoded in get_next_id_pool) will always be used

(FYI, the traditional allocation method is not usable for me because it can re-use UID/GID of deleted users, which can be a security issue)

(from redmine: issue id 2631, created on 2013-08-17, closed on 2013-08-29)

  • Changesets:
    • Revision 23555304 by Côme Chilliet on 2013-08-19T13:13:45.000Z:
Fixes: #2631 Added idAllocationMethod to config backend, fixed nextIdHook behavior
  • Revision 0fb3fee9 by Côme Chilliet on 2013-08-19T13:18:50.000Z:
Fixes: #2631 Added idAllocationMethod to config backend, fixed nextIdHook behavior
  • Custom Fields:
    • Bug in version: 1.0.6
  • Uploads:
    • 0001-Fixes-2631-Added-idAllocationMethod-to-config-backen.patch
Assignee
Assign to
Time tracking