Nov 26 2019
Nov 23 2019
Nov 8 2019
Hi Daniel, Good catch. The 3rd option looks good to me. parse_input_attributes() should probably accept base_dn input for all kind of objects, not only 'ou' (except domain objects). https://git.kolab.org/diffusion/WAP/browse/master/lib/kolab_api_service.php$419
We're taking about this call:
Mar 22 2019
Folders should generally not have a trailing space, so this should be fixed at the input / form level.
Mar 21 2019
Mar 12 2019
"is not equal to" implemented in e55bc13e33af3 [kolab-webadmin master].
Feb 28 2019
Jan 8 2019
Right, the complete fix might be very complicated because:
- we need different filters to list all roles, just non-managed roles or managed roles.
the alternative filters could be:
'(&(objectclass=ldapsubentry)(objectclass=nsComplexRoleDefinition))' - list all non-managed roles
'(&(objectclass=ldapsubentry)(objectclass=nsSimpleRoleDefinition))' - list all manged roles
'(&(objectclass=ldapsubentry)(objectclass=nsRoleDefinition))' - list all roles
- we need a separate code to implement user's roles listing (including editing managed roles). Currently, by default, Kolab User has a nsroledn attribute defined in WAP Settings. That implies that LDAP roles manaement follows logic of getting and changing regular multivalue LDAP attributes, but roles does not work like that. To set a role you need to add or remove nsroledn attribute, but checking role membership nsrole attribute should be used.
I guess, we could change the roles filter to fix the immediate issue, but if we want to display non-managed roles we'll need possibility to list both types of roles, i.e. the filter would depend on what we want to achieve at the moment.
Sep 12 2017
Feb 12 2017
Yes, I agree it's not a software bug, but I propose to add some documentation about delegation to
[which is empty right now]. Something like:
Feb 5 2017
you've to seperate 2 things
Feb 4 2017
Dec 30 2016
Dec 2 2016
Try to add use_tls = true to the [ldap] section to fix the web admin.
Jun 27 2016
That chunk of the config wasn't the culprit here. It's there to make sure resource names are unique - by automatically generating an unique name if already entered name exists.
Apr 30 2016
Apr 29 2016
I did a quick test again, and realized that I can login with a passwort "Test<1234" on Roundcube, but not on Kolab Webadmin. Therefore it must be possible to fix it in wap.
Apr 28 2016
I tried it with a simple php script, and came to the conclusion that the _POST does not work with < character.
Mar 10 2016
Nov 25 2015
No further enhancements to the #HKCCP.