You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: authentication/README.md
+19-17Lines changed: 19 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -150,7 +150,7 @@ If needed, add other domains (eg. the enterprise portal). `OPENID_ALLOWED_DOMAIN
150
150
## #4 Authorization issue
151
151
### 4.1) Symptoms
152
152
153
-
- You have the `rtcAdministrator` role but the `Administration` tab is not displayed in the Business Console,
153
+
- You have the `rtsAdministrator` role but the `Administration` tab is not displayed in the Business Console,
154
154
- or you cannot log in the Business Console at all (if the Helm chart parameter `decisionCenter.disableAllAuthenticatedUser` is set to `true`),
155
155
- or you have at least the `rtsMonitor` role, but you are unable to log in the RES console.
156
156
@@ -308,24 +308,26 @@ The solution is to define the hostname, port, username and password of the proxy
308
308
```
309
309
This needs to be done for each ODM component as the JVM parameters are individually defined for each ODM component.
310
310
311
-
For each ODM component:
311
+
- For each ODM component:
312
312
313
-
1. Retrieve the default JVM parameters from the ConfigMap automatically created and named `<RELEASE_NAME>-odm-<COMPONENT>-jvm-options-configmap` where `<COMPONENT>` is either `dc`, `dr`, `ds-console` or `ds-runtime`:
314
-
```
315
-
kubectl get configmap <RELEASE_NAME>-odm-<COMPONENT>-jvm-options-configmap -o yaml > <COMPONENT>-jvm-options.yaml
316
-
```
313
+
1. Retrieve the default JVM parameters from the ConfigMap automatically created and named `<RELEASE_NAME>-odm-<COMPONENT>-jvm-options-configmap` where `<COMPONENT>` is either `dc`, `dr`, `ds-console` or `ds-runtime`:
314
+
```
315
+
kubectl get configmap <RELEASE_NAME>-odm-<COMPONENT>-jvm-options-configmap -o yaml > <COMPONENT>-jvm-options.yaml
316
+
```
317
317
318
-
1. Edit the .yaml file to add the new JVM parameters above, and change its name to `my-odm-<COMPONENT>-jvm-options-configmap` for instance:
319
-
```
320
-
kubectl apply -f <COMPONENT>-jvm-options.yaml
321
-
```
318
+
1. Edit the .yaml file to add the new JVM parameters above, and change its name to `my-odm-<COMPONENT>-jvm-options-configmap` for instance:
319
+
```
320
+
kubectl apply -f <COMPONENT>-jvm-options.yaml
321
+
```
322
322
323
-
1. Set the Helm chart parameter `jvmOptionsRef` for the ODM component:
323
+
1. Set the Helm chart parameter `jvmOptionsRef` for the ODM component:
324
324
325
-
For instance, for Decision Center:
326
-
```
327
-
decisionCenter:
328
-
jvmOptionsRef: my-odm-dc-jvm-options-configmap
329
-
```
325
+
For instance, for Decision Center:
326
+
```
327
+
decisionCenter:
328
+
jvmOptionsRef: my-odm-dc-jvm-options-configmap
329
+
```
330
+
331
+
- Add `useSystemPropertiesForHttpClientConnections="true"` in `openIdWebSecurity.xml` and update the secret that contains that file.
0 commit comments