RN/Callback/100.0.000.0069 - Revision history

Corinneh: Published

2021-12-22T17:14:35Z

Published

Ed.jamer@genesys.com: Text replacement - "Genesys Multicloud CXment" to "Genesys Engagement"

2021-11-09T21:15:33Z

Text replacement - "Genesys Multicloud CXment" to "Genesys Engagement"

Ed.jamer@genesys.com: Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

2021-11-09T21:12:01Z

Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

Corinne.hicks@genesys.com: Published

2021-09-15T22:09:14Z

Published

Corinne.hicks@genesys.com: Published

2021-09-09T17:31:41Z

Published

New page

{{ComponentRN
|ComponentId=e6de2642-136b-4d94-ac3f-724e317bcbc8
|JQL=issue = GES-2649
|DeploymentTypeId=8b480b3c-2733-433a-9166-eab2c2d0663a
|ReleaseDate=2021-09-09
|PrivateEditionReleaseDate=2021-09-09
|Highlight={{PrivateEditionBoilerplate|Boilerplate=4}}
|Containers=*ges:100.0.000.0069
*ges-100.0.000+0057.tgz
}}
{{Issue
|TicketNumber=GES-2649
|IssueCategoryId=a8930ebb-8e46-4ecd-993f-cdd2d61bc400
|LocalContent=Genesys Engagement Service (GES) now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.

*The Dockerfile has been modified to specify container and file ownership as <tt>user=500</tt> (genesys) and <tt>group=0</tt> (root).
*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=PEC-CAB|version=Current|manual=CABPEGuide|topic=Configure|anchor=securityContext|display text=Configure Genesys Engagement Service}}.
*GES is expected to be deployed using the '''default''' ServiceAccount, which uses the '''restricted''' Security Context Constraint (SCC). If you do not want to use arbitrary UIDs in your OpenShift deployment, you must associate the '''default''' ServiceAccount with the '''genesys-restricted''' SCC, as described in {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=ConfigSecurity|display text=OpenShift security settings}}. If you previously deployed GES using the '''default''' ServiceAccount associated with the '''genesys-restricted''' SCC, you must remove the association if you want OpenShift to use arbitrary UIDs. To do so, execute the following command:
*:<tt>oc adm policy remove-scc-from-user genesys-restricted -z default -n <namespace></tt>
|SupportingDocumentation={{Link-AnywhereElse|product=PEC-CAB|version=Current|manual=CABPEGuide|topic=Configure|anchor=securityContext|display text=Configure Genesys Engagement Service}}
}}

@@ Line 5: / Line 5: @@
 |ReleaseDate=2021-09-09
 |PrivateEditionReleaseDate=2021-09-09
-|Highlight={{PrivateEditionBoilerplate|Boilerplate=4}}
+|Highlight=*{{PrivateEditionBoilerplate|Boilerplate=4}}
 |Containers=*ges:100.0.000.0069
 *ges-100.0.000+0057.tgz
@@ Line 18: / Line 19: @@
 *GES 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 GES using the '''genesys-restricted''' SCC, Genesys recommends that you redeploy GES so that you use arbitrary UIDs.
 |SupportingDocumentation={{Link-AnywhereElse|product=PEC-CAB|version=Current|manual=CABPEGuide|topic=Configure|anchor=securityContext|display text=Configure Genesys Engagement Service}}
 }}

@@ Line 12: / Line 12: @@
 |TicketNumber=GES-2649
 |IssueCategoryId=a8930ebb-8e46-4ecd-993f-cdd2d61bc400
-|LocalContent=Genesys Multicloud CXment Service (GES) now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.
+|LocalContent=Genesys Engagement Service (GES) now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.
 *The Dockerfile has been modified to specify container and file ownership as <tt>user=500</tt> (genesys) and <tt>group=0</tt> (root).
-*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=PEC-CAB|version=Current|manual=CABPEGuide|topic=Configure|anchor=securityContext|display text=Configure Genesys Multicloud CXment Service}}.
+*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=PEC-CAB|version=Current|manual=CABPEGuide|topic=Configure|anchor=securityContext|display text=Configure Genesys Engagement Service}}.
 *GES 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 GES using the '''genesys-restricted''' SCC, Genesys recommends that you redeploy GES so that you use arbitrary UIDs.
-|SupportingDocumentation={{Link-AnywhereElse|product=PEC-CAB|version=Current|manual=CABPEGuide|topic=Configure|anchor=securityContext|display text=Configure Genesys Multicloud CXment Service}}
+|SupportingDocumentation={{Link-AnywhereElse|product=PEC-CAB|version=Current|manual=CABPEGuide|topic=Configure|anchor=securityContext|display text=Configure Genesys Engagement Service}}
 }}