Details
-
Bug
-
Resolution: Done
-
Major
-
7.12.0.GA
-
ER1
-
- set bindCredential with password containing "&"
-
2022 Week 08-10 (from Feb 21)
Description
When KieApp is deployed with LDAP integration by operatpr, if bindCredential contains "&", it fails because generated configuration file is messed up.
Here is a snippet of example CR.
spec: auth: ldap: baseCtxDN: dc=example,dc=com baseFilter: uid bindCredential: P&ssword1 <<<< bindDN: cn=Directory Manager recursiveSearch: true referralMode: FOLLOW roleAttributeID: cn roleFilter: (uniqueMember={1}) roleRecursion: 1 rolesCtxDN: dc=example,dc=com url: ldap://HOST:389 ...
Attachments
Issue Links
- clones
-
RHPAM-4168 Business Central doesn't work with LDAP integration when bindCredential contains "&"
- Closed