Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • user-manual user-manual
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 20
    • Issues 20
    • 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
  • user-manualuser-manual
  • Issues
  • #341
Closed
Open
Issue created Jun 23, 2025 by dockx thibault@tdockxDeveloper

[Orchestrator] - Evolution of configuration file and classes using the organization group definitions

[Orchestrator] - Evolution of configuration file and classes using the organization group definitions

Currently those two lines within fusiondirectory orchestrator : ORCHESTRATOR_TOKEN_BRANCH="ou=orchestrator,ou=tokens,dc=example,dc=com" ORCHESTRATOR_ACCOUNT_BRANCH="ou=dsa,dc=example,dc=com"

It is not required to have them as they can be found within LDAP itself under the configuration of fusiondirectory. They are now defined over there.

We have to change some orchestrator classes as well as its configuration file.

Integrator will be the one being updated to actually retrieve the fusiondirectory configuration.

Assignee
Assign to
Time tracking