Fixing codestyle

issue #5942

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>

Resolve "Listing objects should check ACL on attributes"

See merge request fusiondirectory/fd!79

(cherry picked from commit 9154c4bd)

06ae0efc  feat(objects): Add $checkAcl option on count method as well

Resolve "Listing objects should check ACL on attributes"

See merge request fusiondirectory/fd!78

(cherry picked from commit 12d02686)

f88790fe  fix(objects): Rename var which was hiding an other one

Resolve "Listing objects should check ACL on attributes"

See merge request fusiondirectory/fd!77

(cherry picked from commit 5e9ea3d0)

8c7e4243  fix(objects): Fixed PHP error in objects::ls

Resolve "Listing objects should check ACL on attributes"

See merge request fusiondirectory/fd!75

(cherry picked from commit e9d7d29a)

82fa5126  fix(acl): Checking attributes ACL in objects::ls
893d827c  fix(acl): Checking ACL on attributes used in filters

issue #5775

Now there is an ACL you can put in any ACL role to give access to the
 dashboard.
And all searches from the dashboard are checking ACL and returning info
 only on the data you are allowed to see.
Plugins providing a dashboard tab will have to be adapted as well

issue #5734

This adds an option to check ACLs on filter for count method.
It will be used by webservice plugin.

issue #5732

Two vars were named acl and were colliding, resulting in bugs

issue #5732

issue #5732

objects::ls will now check that the calling user is allowed to read the
 attributes used in the filter.
This will avoid information leak through webservice or custom filter.

issue #5732

Took code from webservice to include directly in objects class.
The point is to make sure objects::ls is not used to see attributes that
 the calling user is not allowed to see.
The same kind of check should be done for the attributes used in the
 filter.
Maybe a bypass should be added later to allow "admins" to use
 operational attributes and other LDAP attributes which does not match
 an ACL.

issue #5732

This allows template to work again since we now test the branch when
 searching for objects.

issue #5722

Resolve "Management filter is broken when mainAttr is FALSE"

Closes #5701

See merge request !24

objects::ls and objects::count now add dn filters based on RDNs to avoid
 false positive when a type use a common objectClass.
Management system may be refactored to use the same system.

issue #5583

There was problems with simpleManagement filters when the mainAttr value
 for one of the objectTypes listed is FALSE.
This was at least a problem for Audit. Maybe ACLs.

closes #5701

Conflicts:
	plugins/personal/roles/class_userRoles.inc

Conflicts:
	include/class_objects.inc

Adapted to the new exception class

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>

Adapted to the new exception class

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>

Remove this unused "$ui" local variable
Remove this unused "$config" local variable

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>

Remove this empty statement.

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>

Use "static" keyword instead of "self"

Signed-off-by: Benoit Mortier <benoit.mortier@opensides.be>

Conflicts:
	include/class_filterLDAP.inc
	include/class_userinfo.inc
	include/functions.inc

Adapted user-filter to match generic name for templates filter