fusiondirectory issueshttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues2019-01-02T10:45:08Zhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/5889Ldap filter parsing issue2019-01-02T10:45:08ZbmortierLdap filter parsing issue### Description
There is an error when using the webservice along with a valid ldap filter and attributes.
### Distribution Name and Version
Debian 9.5
### FusionDirectory Version
1.2-2~jenkinsbuild826
### PHP version used
PHP7
#...### Description
There is an error when using the webservice along with a valid ldap filter and attributes.
### Distribution Name and Version
Debian 9.5
### FusionDirectory Version
1.2-2~jenkinsbuild826
### PHP version used
PHP7
### Origin of php packages
FD
### Steps to Reproduce
Webservice call:
```
CALL: LS [xxx, user, [fdContractStartDate:1, co:1], ou=people,dc=xxx,dc=yyy, (&(fdContractStartDate>=20180820000000Z)(fdContractStartDate<=20180919000000Z))]
ERROR: Could not find ACL for attribute "fdContractStartDate>"
```
**Expected behavior:**
no error, result returnedFusionDirectory 1.3bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/5862filtering and "Unknown element type specified: !"2022-09-01T09:28:58Zbmortierfiltering and "Unknown element type specified: !"### Description
Fatal Error is thrown within a scenario where the search area is used
### Distribution Name and Version
Debian Strech
### FusionDirectory Version
1.2.1-1
### PHP version used
Stock, untouched PHP7 config
### Origi...### Description
Fatal Error is thrown within a scenario where the search area is used
### Distribution Name and Version
Debian Strech
### FusionDirectory Version
1.2.1-1
### PHP version used
Stock, untouched PHP7 config
### Origin of php packages
FD's own repositories
### Steps to Reproduce
Unfortunately, I can only reproduce the following with my specific LDAP content.
It doesn't occur on demo.fusiondirectory.org
1. Navigate to 'users'
2. Use the text area on the right and type a (known) username and click 'apply filter'.
3. Now change to 'systems' section.
4. Navigate back to 'users'
**Expected behavior:**
on step 4, I should get the filtered list of users
**Actual behavior:**
`Fatal error: Uncaught Exception: Unknown element type specified: ! in /usr/share/fusiondirectory/include/class_filter.inc:389 Stack trace: #0 /usr/share/fusiondirectory/include/class_listing.inc(484): filter->render() #1 /usr/share/fusiondirectory/include/simpleplugin/class_simpleManagement.inc(523): listing->render() #2 /usr/share/fusiondirectory/plugins/admin/users/class_userManagement.inc(119): simpleManagement->renderList() #3 /usr/share/fusiondirectory/include/simpleplugin/class_simpleManagement.inc(595): userManagement->renderList() #4 /usr/share/fusiondirectory/include/simpleplugin/class_simpleManagement.inc(1337): simpleManagement->execute() #5 /usr/share/fusiondirectory/plugins/admin/users/main.inc(22): simpleManagement::mainInc('userManagement') #6 /usr/share/fusiondirectory/html/main.php(280): require('/usr/share/fusi...') #7 {main} thrown in /usr/share/fusiondirectory/include/class_filter.inc on line 389`
At this point, if I point the browser to root's FD at /fusiondirectory, I got the red message:
```
Error Fatal error
FATAL: Error when connecting the LDAP. Server said 'Could not bind to (while operating on LDAP server )'.
Please fix the above error and reload the page.
```
If I reload that page, I got the login screen back again where I can login again BUT when I navigate to 'users' section I got the same Fatal Error as before again.
The only way to workaround the problem is to clear the cookie attached to fusiondirectory, and login again.
**Reproduces how often:**
100% but on the said system
### Additional Information
I can provide access to a test instance loaded with this data.FusionDirectory 1.3.1bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/5358Template et photo2022-09-30T21:10:49ZbmortierTemplate et photoRe,
L'ajout d'une photo dans un template ne fonctionne pas/plus
Alexis
*(from redmine: issue id 5358, created on 2017-01-26, closed on 2017-04-05)*
* Changesets:
* Revision 9eca28bb4af0fa4e4b4e36d839d60dcbbd86b03c by Côme Chilliet ...Re,
L'ajout d'une photo dans un template ne fonctionne pas/plus
Alexis
*(from redmine: issue id 5358, created on 2017-01-26, closed on 2017-04-05)*
* Changesets:
* Revision 9eca28bb4af0fa4e4b4e36d839d60dcbbd86b03c by Côme Chilliet on 2017-02-28T14:10:07.000Z:
```
Fixes #5358 Using octetString for templateField to support images as well
```
* Revision e0dc4f5030a0c85528570b07e03ddd0817b887e1 by Côme Chilliet on 2017-03-08T14:14:43.000Z:
```
Fixes #5358 Fixed ImageAttribute usage in templates. Added special %% string start for template values
```
* Revision b631b86ec086a839eb8081057cca609d2a3eb1a8 by Côme Chilliet on 2017-03-09T13:56:02.000Z:
```
Fixes #5358 Using octetString for templateField to support images as well
```
* Revision cf32191124a1ea2e1ef859ce728f42d00c44d97c by Côme Chilliet on 2017-03-09T13:59:54.000Z:
```
Fixes #5358 Fixed ImageAttribute usage in templates. Added special %% string start for template values
Conflicts:
include/class_templateHandling.inc
```
* Custom Fields:
* Bug in version: 1.0.19
* Support contract: Bronze
* Uploads:
* ![image-broken-template5358](/uploads/cf4cf38b562782fdbe9dcc768e8da2e8/image-broken-template5358.png)FusionDirectory 1.1bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/5334when migrating from 1.0.16 to 1.0.19 with the new version of --migrate-dhcp t...2022-09-30T20:07:42Zbmortierwhen migrating from 1.0.16 to 1.0.19 with the new version of --migrate-dhcp there is till a reference not correctedHello,
a customer migrated from 1.0.16 to 1.0.19 and used -migrate-dhcp the entries correctly moved to ou=dhcp but on refererence was still pointing to the old entry
363 cn=zeus,ou=servers,ou=systems,dc=toto,dc=com
cn: zeus
descriptio...Hello,
a customer migrated from 1.0.16 to 1.0.19 and used -migrate-dhcp the entries correctly moved to ou=dhcp but on refererence was still pointing to the old entry
363 cn=zeus,ou=servers,ou=systems,dc=toto,dc=com
cn: zeus
description: dns dhcp ldap -slave
....
objectClass: top
objectClass: goServer
objectClass: GOhard
objectClass: dhcpServer
objectClass: argonautDNSConfig
objectClass: argonautClient
objectClass: fdDNSHost
dhcpServiceDN: cn=dhcp,ou=dhcp,dc=master,dc=fdi
472 cn=dhcp-zeus,ou=dhcp,dc=master,dc=fdi
....
objectClass: top
objectClass: dhcpService
dhcpPrimaryDN: cn=zeus,ou=servers,ou=systems,dc=master,dc=fdi
cn: dhcp-zeus
as you can see the server point correctly to the cn=dhcp-zeus,ou=dhcp,dc=master,dc=fdi point correctly to the correct serveur hosting the dhcp service.
But the server dhcpServiceDN entry was pointing incorrectly to and old service entry not longer existing due to the migration
dhcpServiceDN: cn=dhcp,ou=dhcp,dc=master,dc=fdi
so it seems one entry was not correctly migrated
*(from redmine: issue id 5334, created on 2017-01-23, closed on 2017-04-25)*
* Relations:
* relates #5356
* copied_to #5485
* Changesets:
* Revision f4a67113359cbc8b66e488a762b23a5a9b9fd20c by Côme Chilliet on 2017-01-24T08:55:16.000Z:
```
Fixes #5334 fixed DHCP config DN saved in server after migration
```
* Revision 4996946ca8caa01b253031997785cb69a59db7a3 by Côme Chilliet on 2017-01-24T08:55:55.000Z:
```
Fixes #5334 fixed DHCP config DN saved in server after migration
```
* Revision 9967bc8c79d2e4b84e8ac3267ad950fc8a799e1c by Côme Chilliet on 2017-02-08T14:25:55.000Z:
```
Fixes #5334 fixed DHCP config DN saved in server after migration
```
* Custom Fields:
* Bug in version: 1.0.18
* Support contract: BronzeFusionDirectory 1.1bmortierbmortier