A complete and sovereign open source identity and IT asset management solution that fits perfectly into this identity governance administration approach. Based on the LDAP protocol, FusionDirectory allows you to centralize the management of user accounts, groups, roles and access rights to different resources (business repositories, servers, applications, etc.).
Having become the cornerstone of the information system, the corporate directory is becoming more complex by offering more data and managing more infrastructure services. This interface is simple and allows you to delegate data management completely or partially to non-specialists.
Features
- Users, groups, mail, ssh, personal management
- Supann standards management
- messaging integration of PARTAGE
- System management: dhcp, dns, sudo, all types of systems
- System deployment management: ISP, OPSI Complex role management
- Access to multiple LDAP trees
- Triggers
ACLs and roles
- ACLs are only used by FusionDirectory and not by the underlying LDAP server
- ACLs can be assigned to roles:
- Global administrator: Can do everything
- Local administrator: Can manage users and groups as well as a branch
- Human resources: Can create users from a template to optimize the arrival of new people
- User: Can only modify their data if an administrator authorizes it
Triggers
FusionDirectory integrates a series of triggers that can launch a specific action depending on of a task that FusionDirectory must execute. These triggers are associated with a content type (LDAP user, group, server, password, service) and the triggering action (create, modify, delete, change password, etc.).
For example, when creating a user, a script generation form can be automatically executed with the information from the LDAP server.
This can be useful for generating badges with a photo, a canteen access form or sending an email to notify other departments of the person's actual arrival.
This system is also practical when you want to deploy this person's account on an application that does not support LDAP.
Another example, when a user leaves, you must: archive and delete their mailbox, archive and delete their network space, delete it from third-party applications not connected to LDAP.
All this can be easily done by shell scripts (at least in UNIX environment) and executed automatically after the person is deleted by the administrator in FusionDirectory.
Interaction with non-LDAP applications
FusionDirectory stores the information of a service or server on an LDAP server.
What happens when this service does not have the possibility to interact with LDAP?
This question can be solved by creating:
- A LDAP schema adapted to the application on the LDAP server
- A plugin for its management in FusionDirectory with the simple plugin API
- A FusionDirectory Orchestrator module
We are happy to have been able to sign this contract with 3CT. We appreciate their sense of professionalism and customer service.
