Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory-orchestrator fusiondirectory-orchestrator
  • 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
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectory-orchestratorfusiondirectory-orchestrator
  • Issues
  • #87
Closed
Open
Issue created Apr 28, 2025 by dockx thibault@tdockxMaintainer

[Orchestrator] - Change the DSA authentication within orchestrator to be a binding with LDAP instead

[Orchestrator] - Change the DSA authentication within orchestrator to be a binding with LDAP instead

The goal is to avoid having a password verification or user presence in LDAP verification. If the DSA can simply bind itself to the LDAP, proper permissions will be verified and user will definitely be present and therefore authenticated.

Removing current complexities of allowing specific onset of password hash

Assignee
Assign to
Time tracking