Description of problem:
LDAPUserGroupCallbackImpl and LDAPUserInfoImpl do not replace string

{1} in the role filter with userDN. Right now, they are only able to substitute {0} with username. This may cause some problems when customer utilize LDAP users to log into the Business Central and use LdapExtLoginModule to accomplish that. This module accepts also {1}

parameter in the role filter and so he may expect the same behavior from the Task Service.

Version-Release number of selected component (if applicable):
6.1.0 ER6

Steps to Reproduce:
1. Configure Business Central to utilize LDAP users when working with tasks.
2. Use

{1} parameter in the role filter.
3. Try to perform some task operations.

Actual results:
Nothing is done. The engine is not able to replace {1}

with userDN.

Expected results:
The engine should be able to replace

{1}

with userDN.

Additional info:
https://developer.jboss.org/wiki/LdapExtLoginModule