PEC-Admin/Current/Admin/SSO - Revision history

WikiSysop at 17:46, September 26, 2022

2022-09-26T17:46:13Z

WikiSysop at 19:19, July 28, 2022

2022-07-28T19:19:03Z

Venkatesan.Pavadai.IX: Published

2022-03-31T02:13:07Z

Published

Julie.munn@genesys.com: Published

2021-12-03T14:50:14Z

Published

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

2021-11-09T21:12:38Z

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

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

2021-11-09T20:29:58Z

Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

Brian.marshall@genesys.com: Published

2021-09-07T14:42:21Z

Published

Merav.levy@genesys.com: Published

2021-05-10T15:39:59Z

Published

Merav.levy@genesys.com: Published

2021-04-22T13:23:34Z

Published

Merav.levy@genesys.com: Published

2021-04-22T13:12:48Z

Published

@@ Line 83: / Line 83: @@
 {{!}}Workforce Management
 {{!}}Yes
-{{!}}Not supported for supervisor accounts for administrative activities.
+{{!}}
 {{!}}-
 {{!}}Agent Scripting Administration

@@ Line 18: / Line 18: @@
 Genesys Multicloud CX supports IdP-initiated login using the SAML Single Sign-on integration. With this type of login, you can set up your own portal with links to Genesys Multicloud CX applications. When a user is logged in to your IdP, they can click a link in the portal and directly log in to the Genesys application.
-Set up this functionality in your IdP by providing the URL of the target application as part of the redirect URL. For example, the redirect URL for Agent Desktop would be in this format: <code>redirectUrl=https://<domain>/ui/wwe/index.html</code>
+Set up this functionality in your IdP by providing the URL of the target application as part of the redirect URL. For example, the redirect URL for Agent Workspace would be in this format: <code>redirectUrl=https://<domain>/ui/wwe/index.html</code>
 To get the URL for an application, go to your Genesys Portal page and click the application's widget. Immediately after, press "escape" on your keyboard to prevent the Authentication login page from loading so you can see the application URL in the browser.
@@ Line 33: / Line 33: @@
 !Notes
 {{!}}-
-{{!}}Agent Desktop
+{{!}}Agent Workspace
 {{!}}Yes
 {{!}}
@@ Line 67: / Line 67: @@
 {{!}}Screen Recording
 {{!}}Yes
-{{!}}Supported in Agent Desktop version 9, but not with custom desktops.
+{{!}}Supported in Agent Workspace version 9, but not with custom desktops.
 {{!}}-
 {{!}}Real-Time Reporting (Pulse)

@@ Line 78: / Line 78: @@
 {{!}}-
 {{!}}Recording, Quality Management and Speech Analytics
-{{!}}No
+{{!}}Yes
 {{!}}
 {{!}}-

@@ Line 134: / Line 134: @@
 |structuredtext=Genesys Multicloud CX supports some SAML configuration that must be set up by your Genesys representative:
-*Configure a maximum age for SAML assertion. The default value is 2 hours.
+<!--*Configure a maximum age for SAML assertion. The default value is 2 hours.-->
 *Configure "enforceAuthN" in SAML authentication requests. When enabled, Genesys Multicloud CX's Authentication Service sends an attribute to the IdP that tells it to re-authenticate the user, regardless of their previous state.
 |Status=No

@@ Line 108: / Line 108: @@
 |Status=No
 }}{{Section
-|sectionHeading=Configuring SSO in Genesys Engage
+|sectionHeading=Configuring SSO in Genesys Multicloud CX
 |anchor=engageconfig
 |alignment=Vertical

@@ Line 3: / Line 3: @@
 |DisplayName=Single sign-on
 |TocName=Single sign-on
-|Context=Learn how single sign-on is supported in Genesys Engage cloud.
+|Context=Learn how single sign-on is supported in Genesys Multicloud CX.
 |ComingSoon=No
 |Section={{Section
 |alignment=Vertical
-|structuredtext=Most Genesys Engage cloud applications use single sign-on (SSO) to allow a logged-in user to navigate across supported applications without prompting for credentials again. Genesys Engage cloud can also be configured to use {{#Widget:ExtLink|link=https://en.wikipedia.org/wiki/SAML_2.0|displaytext=SAML 2.0}} for integrations with third-party identity providers (IdP) such as Okta or Google. There are many advantages to enabling SSO in Genesys Engage cloud—for example:
+|structuredtext=Most Genesys Multicloud CX applications use single sign-on (SSO) to allow a logged-in user to navigate across supported applications without prompting for credentials again. Genesys Multicloud CX can also be configured to use {{#Widget:ExtLink|link=https://en.wikipedia.org/wiki/SAML_2.0|displaytext=SAML 2.0}} for integrations with third-party identity providers (IdP) such as Okta or Google. There are many advantages to enabling SSO in Genesys Multicloud CX—for example:
 *Users need to remember only one password.
 *User credentials are managed by a third-party identity provider.
 *Users must have multi-factor authentication by a third-party identity provider for additional security.
-*Users only need to log in once to gain access to Genesys Engage cloud applications that have SSO enabled and non-Genesys applications that use the same identity provider.
+*Users only need to log in once to gain access to Genesys Multicloud CX applications that have SSO enabled and non-Genesys applications that use the same identity provider.
 For details about how a user logs in with SSO, see {{Link-Standalone|topic=PEC-Agent/Login|anchor=sso}}.{{AnchorDiv|idplogin}}
 ===IdP-initiated login===
-Genesys Engage cloud supports IdP-initiated login using the SAML Single Sign-on integration. With this type of login, you can set up your own portal with links to Genesys Engage cloud applications. When a user is logged in to your IdP, they can click a link in the portal and directly log in to the Genesys application.
+Genesys Multicloud CX supports IdP-initiated login using the SAML Single Sign-on integration. With this type of login, you can set up your own portal with links to Genesys Multicloud CX applications. When a user is logged in to your IdP, they can click a link in the portal and directly log in to the Genesys application.
 Set up this functionality in your IdP by providing the URL of the target application as part of the redirect URL. For example, the redirect URL for Agent Desktop would be in this format: <code>redirectUrl=https://<domain>/ui/wwe/index.html</code>
@@ Line 26: / Line 26: @@
 |anchor=support
 |alignment=Vertical
-|structuredtext=View which Genesys Engage cloud applications support SSO.
+|structuredtext=View which Genesys Multicloud CX applications support SSO.
 {{{!}} border="1"
 {{!}}-
@@ Line 118: / Line 118: @@
 *The domain declared in the identity provider metadata should be part of the user name stored within Genesys, to create the most seamless experience. (Example: <tt>john@mycompany.com</tt>) Otherwise, users would need to enter a Tenant or enter the domain before their username. (Example: <tt>mycompany\john</tt>)
-*The username provisioned within Genesys Engage cloud should match the username in the external identity provider.
+*The username provisioned within Genesys Multicloud CX should match the username in the external identity provider.
 |Status=No
 }}{{Section
@@ Line 124: / Line 124: @@
 |anchor=idpconfig
 |alignment=Vertical
-|structuredtext=Genesys Engage cloud must be defined as an application within the identity provider to support the SSO integration.
+|structuredtext=Genesys Multicloud CX must be defined as an application within the identity provider to support the SSO integration.
-Genesys Engage cloud supports the SAML 2.0 protocol as a standard interface to identity providers, and has successfully validated with popular IdPs, including Okta and Ping. Other identity providers can be supported provided they comply with SAML 2.0 and you validate the integration before using in production.
+Genesys Multicloud CX supports the SAML 2.0 protocol as a standard interface to identity providers, and has successfully validated with popular IdPs, including Okta and Ping. Other identity providers can be supported provided they comply with SAML 2.0 and you validate the integration before using in production.
 |Status=No
 }}{{Section
@@ Line 132: / Line 132: @@
 |anchor=saml
 |alignment=Vertical
-|structuredtext=Genesys Engage cloud supports some SAML configuration that must be set up by your Genesys representative:
+|structuredtext=Genesys Multicloud CX supports some SAML configuration that must be set up by your Genesys representative:
 *Configure a maximum age for SAML assertion. The default value is 2 hours.
-*Configure "enforceAuthN" in SAML authentication requests. When enabled, Genesys Engage cloud's Authentication Service sends an attribute to the IdP that tells it to re-authenticate the user, regardless of their previous state.
+*Configure "enforceAuthN" in SAML authentication requests. When enabled, Genesys Multicloud CX's Authentication Service sends an attribute to the IdP that tells it to re-authenticate the user, regardless of their previous state.
 |Status=No
 }}