fusiondirectory-plugins issueshttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues2023-11-16T16:33:39Zhttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6241Private form must not be related to the plugin invitations2023-11-16T16:33:39ZJonathan SwaelensPrivate form must not be related to the plugin invitationsPrivate form must not be related to the plugin invitations.
The code must be read and see the differences again between private / public formPrivate form must not be related to the plugin invitations.
The code must be read and see the differences again between private / public formFusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6251[MAIL] - Modify the direct trigger of sync capabilities for Zimbra and Partage2024-01-25T10:24:37Zdockx thibault[MAIL] - Modify the direct trigger of sync capabilities for Zimbra and Partage~~(Plugins) An update of the plugin tab Mail containing calls to Partage and Zimbra is required, if tick box of "usage of Orchestrator" is set within Supann backend configuration, the plugin should not perform anything itself.~~
It has ...~~(Plugins) An update of the plugin tab Mail containing calls to Partage and Zimbra is required, if tick box of "usage of Orchestrator" is set within Supann backend configuration, the plugin should not perform anything itself.~~
It has been decided to create conditions within Renater and Zimbra plugins to handle this individually.
This allows more flexibility in the case of multiple servers being registered with different behavior required.dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6252[NewPlugin] - Location - Lieu - Allowing specific attributes related to user ...2024-02-19T22:01:36Zdockx thibault[NewPlugin] - Location - Lieu - Allowing specific attributes related to user location to be defined within a new TAB**The general concept**
The idea is a new tab available in the backend of configuration allowing the admins to define :
- Sites
- Building
- Floor
- Desk
Or other required location settings, such as defining (?boolean) usage of supan...**The general concept**
The idea is a new tab available in the backend of configuration allowing the admins to define :
- Sites
- Building
- Floor
- Desk
Or other required location settings, such as defining (?boolean) usage of supann structures.
**Two usages**
_With supann_
The idea is to have the supann structures to have the information about the location, such as site, floor, desks…
This information can be referenced on Entity as well as on Establishment.
Users (File of individual) - can be linked, if using supann, to multiple entities / establishment.
A new tab, location - lieu, will be available with a reduced list of choices based on which entities and / or establishments he is linked with.
_Without supann_
The idea is to have the new tab present on the User (File of individual) with all possible options defined within the backend configuration.
The new plugin would therefore allow usage of the full concept with or without supann attached.dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6253[WebService] - Tokens system to be put in place instead of password usage2024-02-20T15:16:23Zdockx thibault[WebService] - Tokens system to be put in place instead of password usage**The general concept**
The idea is to set in place a new tab on the User, allowing the generation of a token with a specific end date.
The concept is not to use the password to interact with the web service but a defined token.
...**The general concept**
The idea is to set in place a new tab on the User, allowing the generation of a token with a specific end date.
The concept is not to use the password to interact with the web service but a defined token.
We would keep the specific ACL verification currently in place, but the idea is to use a time-driven web service access.
More or less the same behavior as GitLab.
There was an idea to use a "DSA" to interact with FD web service, but DSA is strictly used for LDAP interaction and should not be used with the web service.
**Possible developments**
- Maybe CORE login methodology to add verification of tokens instead of passwords when interacting with web service.
- Web service schema
- New tab on User.
- Logic to be re-defined within web service classes to manage authentication access.
- The token would therefore be the only one used to authenticate.
- Password is to be removed from the allowed authentication logic.FusionDirectory 1.5dockx thibaultdockx thibault