-
Bug
-
Resolution: Done
-
Major
-
7.8.0.GA
-
None
-
False
-
False
-
-
-
-
-
-
CR1
-
+
-
Undefined
-
---
-
---
-
-
2020 Week 43-45 (from Okt 19), 2020 Week 46-48 (from Nov 9)
Customer is using this config map:
```
apiVersion: app.kiegroup.org/v2
kind: KieApp
metadata:
annotations:
app.kiegroup.org: 7.8.1
...
spec:
...
servers:
...
database:
externalConfig:
...
password: foobar$0 #notsecret
```
Openshift RHPAM runs through entrypoint openshift-launch.sh
The yaml template is parsed and set as env variables here and there. finally all end in standalone-openshift.xml
This database password ends in:
```
...
<xa-datasource ...>
...
<security>
...
<password>foobar/opt/eap/bin/openshift-launch.sh</password>
</security>
...
</xa-datasource>
```
Looks like if you use a property like 'foobar$0' $0 gets replaced with script file name.
$0 is the parameter in bash for script file name but only if you put in double quotes.
Looks like we should support that, like property = "$PREFIXfoobar" gets PREFIX replaced.
See:
```
- name: POSTGRESQL_PASSWORD
value: "${KIE_SERVER_POSTGRESQL_PWD}"
```
In that case maybe check if single quotes prevent the replacement. so one can use 'foobar$0' as literal
- is triggering
-
RHPAM-3288 Openshift properties related to passwords in org.kie.server.controller.pwd and org.kie.server.pwd cannot use literal $n
-
- Closed
-
- relates to
-
RHPAM-3431 Openshift properties related to passwords in EJB_TIMER cannot use semicolon literal
-
- Closed
-