fusiondirectory issueshttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues2023-06-12T08:58:21Zhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6282[Core] - Re-structuration of sections and related menu entries2023-06-12T08:58:21Zdockx thibault[Core] - Re-structuration of sections and related menu entries### Requirements
In order to be more user-friendly, we decided to restructure elements from section and menu entries.
## Descriptive title for this contribution
[Core] - Re-structuration of sections and related menu entries
### Step ...### Requirements
In order to be more user-friendly, we decided to restructure elements from section and menu entries.
## Descriptive title for this contribution
[Core] - Re-structuration of sections and related menu entries
### Step by step description of this contribution
Below list of new sections and related entries.
- Configuration
- - Configuration
- - Abonnement (fd-plugins)
- - Informations du serveur GPG (fd-plugins)
- - Modèle de mail
- - Tâches
- Dashboard
- - Argonaut (fd-plugins)
- - Plugin manager
- - Tableau de bord des tâches
- - Objets d'inventaire (fd-plugins)
- Rapports
- - Audit (fd-plugins)
- - Aide au débogage (fd-plugins)
- Export / import
- - Import / Export LDAP (fd-plugins)
- - Importation OPSI (fd-plugins)
_Source directory would therefore change as follow_
FD_PATH/plugins/addons would become
FD_PATH/plugins/
- configuration
- config -> configuration/config
- addons/subscription/ -> configuration/subscription (fd-plugins)
- addons/gpg/ -> configuration/gpg/ (fd-plugins)
- addons/mailtemplate/ -> configuration/mailtemplate/
- addons/tasks/ -> configuration/tasks
-
- dashboard
- addons/argonaut/ -> dashboard/argonaut (fd-plugins)
- addons/pluginsManager/ -> dashboard/pluginmanager
- admin/tasks/ -> dashboard/tasks/
- reports
- admin/audit/ -> reports/audit
- addons/debugHelp/ -> reports/debughelp (fd-plugins)
- export
- addons/ldapmanager/ -> export/ldapmanager (fd-plugins)
- addons/opsi/ -> export/opsi (fd-plugins)
- generic
- addons/ldapdump/ -> generic/ldapdump/ (fd-plugins)
-
EDIT 1 : For the full above list of folder modication and new location, refer to the cloned issue within plugins.
EDIT 2 : In order to be aligned with the numbering of section and priorities, below list is to be taken as reference.
- Users and Groups - 0
- Systems - 10
- Configuration 20
- Dashboard 30
- Reporting 40
- Export / Import 50
- My account 60
### Schemas needed by this contribution
No new schemas should be required
### Benefits
Better logical view.
### Possible Drawbacks
None
### Actual use cases
NoneFusionDirectory 1.4dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6281[PluginManager] - move the plugin tab from dasboard to the left menu under da...2023-06-01T15:50:09Zbmortier[PluginManager] - move the plugin tab from dasboard to the left menu under dashboard sectionHello,
The plugin tab from dashboard should be moved to the left menu configuration under ~~configuration~~ Dashboard section to have a place where we can see directly the plugins installed
Cheers
Note : Such as below
- Dashboard
-...Hello,
The plugin tab from dashboard should be moved to the left menu configuration under ~~configuration~~ Dashboard section to have a place where we can see directly the plugins installed
Cheers
Note : Such as below
- Dashboard
-- Plugin manager
-- Tableau de bord des tâches
-- Objets d'inventaireFusionDirectory 1.4dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6270[Snapshot] - Enhancement in order to provide a first concept of revision and ...2023-04-20T18:25:45Zbmortier[Snapshot] - Enhancement in order to provide a first concept of revision and source reference### Requirements
New configuration items must be introduced.
Must work with LSC / web services queries.
See below actual and expected in order to have a more broad idea of the requirements.
## Descriptive title for this enhancement
[S...### Requirements
New configuration items must be introduced.
Must work with LSC / web services queries.
See below actual and expected in order to have a more broad idea of the requirements.
## Descriptive title for this enhancement
[Snapshot] - Enhancement in order to provide a first concept of revision and source reference
### Actual behavior
Snapshot is a manual operation and has not concept of retention nor origin of data sources.
### Expected behavior
It must be able to have a concept of retention date as well as minimum number of "revisions" to be kept.
A new attribute containing the origin of the source must be present.
The backend configuration should reflect the changes for snapshot, allowing the above configuration as well as adding the possibility to automate the creation of snapshot upon account save.
### Step by step description of new behavior
A possible new tab within configuration must be created (snapshot), adding :
- Retention date.
- Minimum retention.
- Automatic snapshot.
A possible new tab within configuration must be created (aggregation?), adding :
- The possibility to add the origin/source of the received data.
When creating a snapshot, there would be an invisible option (only in the GUI) allowing LSC or web service queries to specify the origin of the data.
### Benefits
One of the many possible benefits would be to allow aggregation and disaggregation.
Knowing the source of the data allows creating a trust level. (To be developed).
### Possible Drawbacks
None.
### Applicable Issues
NoneFusionDirectory 1.5bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6241[Icons] Proper icons for tasks - task dashboard - mail template2023-03-09T11:38:55Zbmortier[Icons] Proper icons for tasks - task dashboard - mail template### Requirements
Proper icons for added features is required.
## Descriptive title for this enhancement
[Icons] Proper icons for tasks - task dashboard - mail template
### Actual behavior
No proper icons exist.
### Expected behavio...### Requirements
Proper icons for added features is required.
## Descriptive title for this enhancement
[Icons] Proper icons for tasks - task dashboard - mail template
### Actual behavior
No proper icons exist.
### Expected behavior
Proper icons are showned.
### Step by step description of new behaviour
Simply show new icons.
### Benefits
Proper icons for added features
### Possible Drawbacks
None
### Applicable IssuesFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6231[Tasks-Dashboard] - Develop a new dashboard for tasks to allow granular statu...2022-12-05T11:32:05Zbmortier[Tasks-Dashboard] - Develop a new dashboard for tasks to allow granular status report on sub-tasks### Requirements
It is being clear that a new dashboard with proper status report with sub-tasks is required.
For example : When a task mail is created, all e-mails sent should have their own status being clearly visible within a dashb...### Requirements
It is being clear that a new dashboard with proper status report with sub-tasks is required.
For example : When a task mail is created, all e-mails sent should have their own status being clearly visible within a dashboard.
## Descriptive title for this enhancement
[Tasks-Dashboard] – Develop a new dashboard for tasks to allow granular status report on sub-tasks
### Actual behavior
Within the Tasks menu, the main status of the task is reported, but not the underlying sub-tasks.
The status of the main task is being updated. Not the sub-tasks.
### Expected behavior
A proper report on each and individual sub-tasks. Starting first with e-mails tasks.
A new dashboard menu for tasks under dashboard section.
### Step by step description of new behaviour
When a sub-tasks has been processed, example : a mail.
A proper report of the status of that email must be seen within Fusion Directory Tasks Dashboard.
### Benefits
Allows to have better granularity on every tasks status created and to act upon failure of a sub-tasks if required.
### Possible Drawbacks
None
### Applicable Issues
NoneFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6207Creation of new Class - Tasks Object - standard2023-03-09T14:56:32ZbmortierCreation of new Class - Tasks Object - standard### Requirements
There is a need to be able to schedule multiple tasks. Tasks must be specialized depending on the type of it.
A main management page defined below Mail Template within Configuration section of FD.
This management page ...### Requirements
There is a need to be able to schedule multiple tasks. Tasks must be specialized depending on the type of it.
A main management page defined below Mail Template within Configuration section of FD.
This management page can be inspired by "deployment", as it would reflect on the status and types of the listed tasks.
A configuration page (as TAB) within FD-Configuration will be created in order to defined the base.
(For now).
The first page of a Task Creation will be generic, the content of it will evolve during development.
For now, only the name of the task is required. (Maybe the schedule of the task can already be defined).
A tab needs to be added next to the first page, named : "E-Mail"
It will be used to link an existing mail template object and a list of users or groups therefore creating a task of type "Mail".
Tasks requires is own LDAP Schema. Following numbering can be used.
1.3.6.1.4.1.38414.89.0.0
*An update of the documentation is required
## Descriptive title for this enhancement
Creation of new Class - Tasks Object - standard
### Actual behavior
Nothing exists managing tasks
### Expected behavior
Possible to manage and keep tracks of tasks.
Execute and manage the tasks.
### Step by step description of new behavior
Click on Tasks below Mail Template within configuration section.
Manage the list of existing tasks or create a new one.
### Benefits
We can schedule tasks and have a better managements of redundant manual tasks.
### Possible Drawbacks
None.
### Applicable Issues
None.FusionDirectory 1.4bmortierbmortier2022-06-01https://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6204Enhancement - Mail Template Object - User Reminder2022-10-19T14:46:21ZbmortierEnhancement - Mail Template Object - User Reminder### Requirements
Enhancement of Mail Template object including _User Reminder_.
Basic fields with _%macro%_ defined {token / key / ...} as string (processing will be done when _task_ is created)
## Descriptive title for this enhanceme...### Requirements
Enhancement of Mail Template object including _User Reminder_.
Basic fields with _%macro%_ defined {token / key / ...} as string (processing will be done when _task_ is created)
## Descriptive title for this enhancement
**Enhancement - Mail Template Object - User Reminder**
### Actual behavior
_Possibility to reach Mail Template within the configuration menu of FD._
_Possibility to fulfill a mail template and to save the required data within its own LDAP schema._
### Expected behavior
Possible to save a mail template and retrieve it.
A mechanism called task will developed in order to process properly the selected mail template.
On top of the normal mail standard object, some new fields are available via User Reminder TAB.
Only one User Reminder type of mail template can be created.
### Step by step description of new behavior
1. Open FD main page.
2. Within configuration menu, click on mail template
3. Fills the different available fields of the main page
4. Select the User Reminder TAB and fills the different available fields.
5. Save the mail template.
**Important**
_No User Recovery no User Reminder can be created twice, nor created within the same mail object template._
### Benefits
Mail Template user reminder is available within mail template.
### Possible Drawbacks
None.
### Applicable Issues
None.bmortierbmortier2022-05-09https://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6202Creation of new Class - Mail Template Object - Standard2023-03-09T14:58:36ZbmortierCreation of new Class - Mail Template Object - Standard### Requirements
New Mail Template Object concept.
A standard generic mail object that can be easily extended.
Standard Fields :
- MailTemplateCN
- Subject
- Body
- Signature
- Attachment
- ReadReceipt.
A configuration must be avail...### Requirements
New Mail Template Object concept.
A standard generic mail object that can be easily extended.
Standard Fields :
- MailTemplateCN
- Subject
- Body
- Signature
- Attachment
- ReadReceipt.
A configuration must be available within FD configuration plugins sub-menus.
The schema to be used : `Prefix ‘1.3.6.1.4.1.38414’ - '88.1.1'`
## Descriptive title for this enhancement
**Creation of new Class - Mail Template Object**
### Actual behavior
Possibility to reach Mail Template within the configuration menu of FD.
Possibility to fulfill a mail template and to save the required data within its own LDAP schema.
### Expected behavior
Possible to save a mail template and retrieve it.
A mechanism called task will developed in order to process properly the selected mail template.
### Step by step description of new behavior
1. Open FD main page.
2. Within configuration menu, click on mail template
3. Fills the different available fields.
4. Save the mail.
---
1. Open FD main page.
2. Within the FD configuration plugins, click on mail template
3. Configure the base for mail template
4. Save configuration
### Benefits
Mail Template generic/standard structure created.
### Possible Drawbacks
None.
### Applicable Issues
None.FusionDirectory 1.4bmortierbmortier2022-05-03https://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6196Improve contribution by adding a simple way to add / delete plugin2023-05-02T08:40:33ZbmortierImprove contribution by adding a simple way to add / delete plugin### Requirements
Integrate the CI of FusionDirectory is too complicated for other persons who wants to contribute for several reasons :
- code is stored in another site
- lifecyle is different of FusionDirectory's
## Descriptive t...### Requirements
Integrate the CI of FusionDirectory is too complicated for other persons who wants to contribute for several reasons :
- code is stored in another site
- lifecyle is different of FusionDirectory's
## Descriptive title for this enhancement
Add a way to integrate easily contribution trough a dedicated plugin management tool
### Actual behavior
a poor fusiondirectory-setup tools:
- no way to list all plugin installed
- no way to check installation
- no way to check dependencies
### Expected behavior
see : https://github.com/gallak/fusiondirectory-plugins-pluginsmanager
I used a pivot file control.yaml inspired from Debian control file
This file could be used for supplying data inside a futur "market place"
### Step by step description of new behaviour
1. create a pivot file per plugin ( see syntax : https://github.com/gallak/fusiondirectory-plugins-pluginsmanager)
2. used this file for supplying data in market
3. used this file to manage plugin inside FD instance.
### Benefits
more visibility to FusionDirectory plugin list
more capabilities to accept contribution outside of Fusiondirectory Project
### Possible Drawbacks
Keep a clear communication about support communication
So I'll be happy to see it in core !FusionDirectory 1.4bmortierbmortier2023-01-31https://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6181GivenName mandatory in FusionDirectory for the user but not mandatory in open...2021-08-25T14:53:41ZbmortierGivenName mandatory in FusionDirectory for the user but not mandatory in openldap schema## Descriptive title for this enhancement
<!-- required -->
GivenName mandatory in FusionDirectory for the user but not mandatory in openldap schema, and in some case givenName is not used in some LDAP directories so this cause an issu...## Descriptive title for this enhancement
<!-- required -->
GivenName mandatory in FusionDirectory for the user but not mandatory in openldap schema, and in some case givenName is not used in some LDAP directories so this cause an issue
### Actual behavior
<!-- What actually happens -->
Actually givenName is mandatory in FusionDirectory because its used in the creation of the cn of the user, see field «CN pattern» in configuration.
### Expected behavior
<!-- What you expect to happen-->
Make givenName optional if the option is selected in the FusionDirectory Config
### Step by step description of new behaviour
<!-- Required -->
1. Add a checkbox to select if givenName is mandatory or not
2. The checkbox should be selected by default meaning givenName is mandatory, to not change the actual way of working
3. If checkbox is not selected it means givenName is not mandatory
4. If checkbox is not selected we should check «CN pattern» in configuration and trigger an error if %givenName% is used
### Benefits
<!-- optional -->
<!-- What benefits will be realized by the code change? -->
allow people that need to have a blank givenName to be able to use FusionDirectory, the need has been discussed with a customer
### Possible Drawbacks
<!-- optional -->
<!-- What are the possible side-effects or negative impacts of the code change? -->
Difficulties with checking «CN pattern» in configuration and interface where we have to remove the red asterisk within givenName on the user interfaceFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6169Issue a warning if sizelimit or number of entries is higher than max_input_va...2021-06-17T09:49:12ZbmortierIssue a warning if sizelimit or number of entries is higher than max_input_vars PHP ini setting### Description
When adding 1000+ users to a group, I got this error:
```
Fatal error: Uncaught FusionDirectoryException: CSRF protection token missing in /usr/share/fusiondirectory/include/class_CSRFProtection.inc:29 Stack trace: #0 /u...### Description
When adding 1000+ users to a group, I got this error:
```
Fatal error: Uncaught FusionDirectoryException: CSRF protection token missing in /usr/share/fusiondirectory/include/class_CSRFProtection.inc:29 Stack trace: #0 /usr/share/fusiondirectory/html/main.php(59): CSRFProtection::check() #1 {main} thrown in /usr/share/fusiondirectory/include/class_CSRFProtection.inc on line 29
```
### Distribution Name and Version
Debian 10
### FusionDirectory Version
1.3.1
### PHP version used
<!-- Required -->
7.3.27
### Origin of php packages
Distribution packages
### Steps to Reproduce
1. Create a group
2. Add 1000+ members
**Expected behavior:**
Members should be added to the group
**Actual behavior:**
PHP Fatal Error
**Reproduces how often:**
100% of time
### Additional Information
None.FusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6152Add subscription screen2023-06-23T20:02:17ZbmortierAdd subscription screenThe idea is to have a «Subscription» page in the menu (with its own ACLs), showing either information about how to get a subscription, or information about the subscription stored in the LDAP.
It must be able to import this information f...The idea is to have a «Subscription» page in the menu (with its own ACLs), showing either information about how to get a subscription, or information about the subscription stored in the LDAP.
It must be able to import this information from a file sent to subscribers, not sure yet if it should be LDIF or JSON. Apart from the import field, information is read-only.
The information is stored under ou=fusiondirectory.FusionDirectory 1.3.1bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6150Add a configuration option to enable CAS verbose mode2021-02-15T15:52:01ZbmortierAdd a configuration option to enable CAS verbose modeWithout verbose mode phpCAS will only give unhelpful generic errors.Without verbose mode phpCAS will only give unhelpful generic errors.FusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6145We need a modifier to generate valid uids2021-03-24T20:20:31ZbmortierWe need a modifier to generate valid uidsWith current modifiers it is quite hard to write a macro that will generate a valid uid from a random name.
The modifier `a` will remove non-ascii characters but not spaces and quotes.
The idea is to add a «mode» parameter to the `a` m...With current modifiers it is quite hard to write a macro that will generate a valid uid from a random name.
The modifier `a` will remove non-ascii characters but not spaces and quotes.
The idea is to add a «mode» parameter to the `a` modifier, defaulting to `ascii`, and with an alternate `uid` mode, which removes everything that is not allowed in an uid, depending on strict mode configuration.
It should remove spaces, quotes, accents, and convert to lowercase as well, so that only one modifier is needed for simple uid generation.
`%a[uid]|sn%` instead of `%alp|sn%`FusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6128Rewrite fusiondirectory-insert-schema based on ldap-config-manager2023-02-02T11:44:36ZbmortierRewrite fusiondirectory-insert-schema based on ldap-config-managerPerl tool ldap-schema-manager is replaced by PHP tool ldap-config-manager.
fusiondirectory-insert-schema should be rewritten to be based on ldap-config-manager but have an interface as close as possible to the previous one.
This means ...Perl tool ldap-schema-manager is replaced by PHP tool ldap-config-manager.
fusiondirectory-insert-schema should be rewritten to be based on ldap-config-manager but have an interface as close as possible to the previous one.
This means we need to add schema list support into ldap-config-manager which only accepts to insert schema one by one currently.FusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6125add an option to output clear password when we use --encrypt-passwords2021-09-14T12:55:17Zbmortieradd an option to output clear password when we use --encrypt-passwords## Descriptive title for this enhancement
add an option to fusiondirectory-setup to output clear password when we use --encrypt-passwords
### Actual behavior
Not implemented
### Expected behavior
fusiondirectory-setup --check-config...## Descriptive title for this enhancement
add an option to fusiondirectory-setup to output clear password when we use --encrypt-passwords
### Actual behavior
Not implemented
### Expected behavior
fusiondirectory-setup --check-config-password <environment(default = default)>
displays
my_clear_password
### Step by step description of new behaviour
<!-- Required -->
1. Add the option
### Benefits
- Admins inheriting FD installations can decrypt password
- Automation tools like Ansible or puppet have a way to validate a password against the encrypted one without crafting clear password config and reencrypt on each run (showing a change when there is not)
- For the previous point leaving encryption to FD is better than let 3rd party tools mimic FD behavior, leading to an obsolete tooling if you decide to change the encryption process
### Possible Drawbacks
- This code change the argument reading loop and may have undesired side effects (though it shouldn't)
- A simple way to decrypt password for an attacker (but reading at the tool perl source is easy enough to do it without)FusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6124Rewrite fusiondirectory-setup cli tool in PHP2023-02-02T11:29:26ZbmortierRewrite fusiondirectory-setup cli tool in PHP## Descriptive title for this enhancement
<!-- required -->
rewrite the fusiondirectory-setup in php
### Actual behavior
<!-- What actually happens -->
actually fusiondirectory-setup is in perl but its difficult to support and in ce...## Descriptive title for this enhancement
<!-- required -->
rewrite the fusiondirectory-setup in php
### Actual behavior
<!-- What actually happens -->
actually fusiondirectory-setup is in perl but its difficult to support and in certains distributions like centos 8 support for perl is suboptimal
### Expected behavior
<!-- What you expect to happen-->
be able to convert fusiondirectory-setup to an php porgram run by php-cli
### Step by step description of new behaviour
<!-- Required -->
1. [First Step]
2. [Second Step]
3. [and so on...]
### Benefits
<!-- optional -->
<!-- What benefits will be realized by the code change? -->
be able to remove all perl dependancies, and use the ldap lib created in [ldap-config-manager](https://gitlab.fusiondirectory.org/fusiondirectory/schema2ldif)
### Possible Drawbacks
<!-- optional -->
<!-- What are the possible side-effects or negative impacts of the code change? -->
replacement of perl libraries with core perl libraries
### Restrictions
<!-- optional -->
<!-- Enter any applicable Issues here -->
* we should use all core php libraries and avoid using external one
* If we use external one we should check that they run correctly on all the targte os : debian 9-10/ubuntu 16-18-20/centos 7-8FusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6119Add core features for Archive plugin2021-02-09T08:35:43ZbmortierAdd core features for Archive pluginThe archive system from fd-plugins#6075 needs code in core for the following bits:
- Add Archive action in management menu
- Add ACL class for archive rights
- Search for archived fields in unicity checks
- Add an API function to delete...The archive system from fd-plugins#6075 needs code in core for the following bits:
- Add Archive action in management menu
- Add ACL class for archive rights
- Search for archived fields in unicity checks
- Add an API function to delete objects without deletion ACL rightsFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6105Add option ldif-wrap=no in class_ldap.inc2021-01-28T17:09:17ZbmortierAdd option ldif-wrap=no in class_ldap.inc## Descriptive title for this enhancement
Add option ldif-wrap=no in class_ldap.inc
### Actual behavior
Actually ldapsearch is performed without the option
### Expected behavior
It would be nice to add the option or having a way to ...## Descriptive title for this enhancement
Add option ldif-wrap=no in class_ldap.inc
### Actual behavior
Actually ldapsearch is performed without the option
### Expected behavior
It would be nice to add the option or having a way to activate the option
### Step by step description of new behaviour
1. Edit class_ldap.inc
2. Add ldif-wrap=no in the cmd
```
# before
$cmd = 'ldapsearch'.($this->tls ? ' -ZZ' : '')." -x -LLLL -D {$admin} {$filter} {$limit} {$scope} -H {$host} -b {$dn} -w {$pwd} ";
# after
$cmd = 'ldapsearch'.($this->tls ? ' -ZZ' : '')." -o ldif-wrap=no -x -LLLL -D {$admin} {$filter} {$limit} {$scope} -H {$host} -b {$dn} -w {$pwd} ";
```
### Benefits
The ldif will no more contain wrap it can ease replace operation because we not need to think that the line can be split
### Possible Drawbacks
NoneFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6102Add a modifier for incremental number2021-02-04T11:08:59ZbmortierAdd a modifier for incremental numberCurrent number modifier checks unicity in the LDAP, and increments as many times as necessary, which may end up being quite slow if a lot of values are already taken.
An incremental number modifier would instead store the last used valu...Current number modifier checks unicity in the LDAP, and increments as many times as necessary, which may end up being quite slow if a lot of values are already taken.
An incremental number modifier would instead store the last used value in the LDAP configuration and increment from there.FusionDirectory 1.4bmortierbmortier