RN/GenesysWeb Services and Applications/9.0.002.98 - Revision history

WikiSysop at 13:01, May 4, 2022

2022-05-04T13:01:29Z

Julie.munn@genesys.com: Published

2021-11-12T13:48:56Z

Published

Julie.munn@genesys.com: Published

2021-10-29T20:22:24Z

Published

Julie.munn@genesys.com: Published

2021-09-17T22:29:49Z

Published

New page

{{ComponentRN
|ComponentId=d8ae146d-0abb-4c7e-8a14-3be0a382a3d5
|JQL=issuekey = GAPI-30097
|DeploymentTypeId=8b480b3c-2733-433a-9166-eab2c2d0663a
|ReleaseDate=2021-09-17
|PrivateEditionReleaseDate=2021-09-17
|Highlight={{PrivateEditionBoilerplate|Boilerplate=4}}
|Containers=*gws-app-provisioning:9.0.000.98
*gws-app-workspace:9.0.000.93
*gws-platform-configuration:9.0.000.83
*gws-platform-datacollector:9.0.000.53
*gws-platform-ixn:9.0.000.46
*gws-platform-ocs:9.0.000.49
*gws-platform-setting:9.0.000.55
*gws-platform-statistics:9.0.000.64
*gws-platform-voice:9.0.000.69
*gws-system-nginx:9.0.000.19
*gws-ui-crmworkspace:9.0.000.65
*gws-ui-provisioning:9.0.000.89
*gws-ui-workspace:9.0.000.86

Helm charts:

*gws-ingress-1.0.12.tgz
*gws-monitoring-1.0.21.tgz
*gws-services-1.0.55.tgz
*wwe-nginx-9.0.4.tgz
}}
{{Issue
|TicketNumber=GAPI-30097
|IssueCategoryId=a8930ebb-8e46-4ecd-993f-cdd2d61bc400
|LocalContent=Web Services and Applications now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.

*The securityContext settings exposed in the default '''values.yaml''' file specify the user and group IDs for the genesys user (<tt>500:500:500</tt>). You must override these Helm chart values if you want OpenShift to use arbitrary UIDs. For more information, see {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=ConfigSecurity}}.
*Web Services and Applications is deployed using ServiceAccounts that use the '''restricted''' Security Context Constraint (SCC). In an earlier implementation, Genesys required you to deploy all private edition services using a ServiceAccount associated with the custom '''genesys-restricted''' SCC, to control permissions for the genesys user (500). Genesys now expects OpenShift to use arbitrary UIDs in your deployment, and the '''genesys-restricted''' SCC has been deprecated. If you previously deployed Web Services and Applications using the '''genesys-restricted''' SCC, Genesys recommends that you redeploy Web Services and Applications so that you use arbitrary UIDs.
}}

@@ Line 31: / Line 31: @@
 |TicketNumber=GAPI-30097
 |IssueCategoryId=a8930ebb-8e46-4ecd-993f-cdd2d61bc400
-|LocalContent=Web Services and Applications now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.
+|LocalContent=Genesys Web Services and Applications now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.
 *The securityContext settings exposed in the default '''values.yaml''' file specify the user and group IDs for the genesys user (<tt>500:500:500</tt>). You must override these Helm chart values if you want OpenShift to use arbitrary UIDs. For more information, see {{Link-AnywhereElse|product=GWS|version=Current|manual=GWSPEGuide|topic=Configure}}.
-*Web Services and Applications is deployed using ServiceAccounts that use the '''restricted''' Security Context Constraint (SCC). In an earlier implementation, Genesys required you to deploy all private edition services using a ServiceAccount associated with the custom '''genesys-restricted''' SCC, to control permissions for the genesys user (500). Genesys now expects OpenShift to use arbitrary UIDs in your deployment, and the '''genesys-restricted''' SCC has been deprecated. If you previously deployed Web Services and Applications using the '''genesys-restricted''' SCC, Genesys recommends that you redeploy Web Services and Applications so that you use arbitrary UIDs.
+*Genesys Web Services and Applications is deployed using ServiceAccounts that use the '''restricted''' Security Context Constraint (SCC). In an earlier implementation, Genesys required you to deploy all private edition services using a ServiceAccount associated with the custom '''genesys-restricted''' SCC, to control permissions for the genesys user (500). Genesys now expects OpenShift to use arbitrary UIDs in your deployment, and the '''genesys-restricted''' SCC has been deprecated. If you previously deployed Genesys Web Services and Applications using the '''genesys-restricted''' SCC, Genesys recommends that you redeploy Genesys Web Services and Applications so that you use arbitrary UIDs.
 }}
 {{Issue

@@ Line 5: / Line 5: @@
 |ReleaseDate=2021-09-17
 |PrivateEditionReleaseDate=2021-09-17
-|Highlight={{PrivateEditionBoilerplate|Boilerplate=4}}
+|Highlight=*{{PrivateEditionBoilerplate|Boilerplate=gke-eap-high}}
 |Containers=*gws-app-provisioning:9.0.000.98
 *gws-app-workspace:9.0.000.93
@@ Line 34: / Line 35: @@
 *The securityContext settings exposed in the default '''values.yaml''' file specify the user and group IDs for the genesys user (<tt>500:500:500</tt>). You must override these Helm chart values if you want OpenShift to use arbitrary UIDs. For more information, see {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=ConfigSecurity}}.
 *Web Services and Applications is deployed using ServiceAccounts that use the '''restricted''' Security Context Constraint (SCC). In an earlier implementation, Genesys required you to deploy all private edition services using a ServiceAccount associated with the custom '''genesys-restricted''' SCC, to control permissions for the genesys user (500). Genesys now expects OpenShift to use arbitrary UIDs in your deployment, and the '''genesys-restricted''' SCC has been deprecated. If you previously deployed Web Services and Applications using the '''genesys-restricted''' SCC, Genesys recommends that you redeploy Web Services and Applications so that you use arbitrary UIDs.
 }}