Revision as of 14:44, October 2, 2017 by Djudge (talk | contribs)
Jump to: navigation, search

Genesys Portal

Information.png Note: Not all changes listed below may pertain to your deployment.

March 18, 2016 (8.5.200.34)

What's New

OpenID Connect 1.0 (Implicit Flow) support for Azure Active Directory

  • Genesys Hub Single Sign-On (SSO) now supports Azure Active Directory OpenID connect authentication (Implicit Flow).

Azure Active Directory Signing Key Rollover support

  • Genesys Hub Single Sign-On (SSO) now supports automatic Azure Active Directory Signing Key Rollover.

March 18, 2016 (8.5.200.24)

What's New

Multiple identity support

  • IdP proxy now supports multiple usernames to be remembered in the browser. Previously, only one username was saved.

IDP Proxy domain handling improved

  • IdP Proxy now improves its username handling in several places:
    IdP Proxy now trims leading and trailing spaces in the username.
    IdP Proxy now reports a more meaningful error if the user's domain cannot be recognized.

Hardcoded timeout increased

  • The default value for 'MaxAuthenticationAge' has been increased to 120 days. Previously, it was two hours, which caused issues for customers who have a long authentication live time from their IdPs.

March 18, 2016 (8.5.200.20)

What's New

Name change

  • The name Genesys Hub changed to Genesys Portal. All occurrences of Hub have been replaced by Portal.

Layout change

  • The layout of the Portal applications changed from a tile format to a list format. The new design includes vertical sections for each of the application groups, which show the applications in rows that adjust according to the browser width.

March 18, 2016 (8.5.200.16)

What's New

Support SP metadata dynamical loading

  • Genesys IdP now supports dynamical SP metadata loading by the new FolderMetadataProvider metadata provider type. Once FolderMetadataProvider is configured in the relying-party.xml, Genesys IdP monitors the metadata folder and dynamically refreshes any SP metadata files that are added, updated or removed in the folder.

March 18, 2016 (8.5.200.11)

What's New

Support username mapping

  • During external IdP authentication, Portal Single Sign-On (SSO) now provides limited support for the mapping of external usernames to Genesys internal usernames. External usernames can be in the form of a uid (the local part of an email address) or a full email address. Genesys internal usernames must be in the form of a full email address that uniquely identifies the user account in the Genesys system, and the local part must be the same as the external username. The domain part must include a unique customer identification, while inclusion of a role extension is optional. Username mapping is only available when the IdP application option ‘externalAuthentication\singleTenant’ is set to ‘false’.
    Users will be required to provide their Genesys internal username once, which will then be remembered by the Portal. Their external username will be mapped to the internal username by the local part only.

March 18, 2016 (8.5.200.10)

What's New

Support external IdP

  • Support is now available to allow Portal Single Sign-On (SSO) by using the customer’s external IdP for authentication purposes. LDAP is no longer required in this configuration. Shibboleth IDP acts as a proxy (aka. IdP proxy) between Genesys applications (SPs) and the external IdP. SPs authenticate to IdP proxy as they did before. IdP proxy forwards the SAML authentication request to the external IdP and responds accordingly based on the authentication result from the external IdP.

March 18, 2016 (8.5.200.10)

What's New

Persistent Terms and Conditions acceptance

  • If the Terms and Conditions has been enabled, users now accept it once and the acceptance will be saved, so the same user does not need to accept it again. Previously, the user had to accept it every time.

March 18, 2016 (8.5.000.05)

What's New

Resolved Issues

  • Hidden is now available as a parameter to status. When Hidden is selected as a status for a Widget, this Widget icon is hidden on the Landing Page. (GH-217)
  • A Recording widget/icon is included on the Genesys Portal Landing Page in preparation of pending Genesys Interaction Recording deployment. (GH-216)
  • Sample files HubWidgets_Production_Sample.json and HubWidgets_Staging_Sample.json are available for Staging and Production in Portal Landing Page. (GH-214)
  • The Genesys Portal Landing Page Help is updated with role-based help links to Genesys Cloud Help, the Agent's Guide, the Supervisor's Guide, the Manager's Guide, and the Administrator's Guide. (GH-213)
  • The Genesys Portal Landing Page footer version number now supports 7-digit version. (GH-204)

March 18, 2016 (8.5.000.00)

What's New

Genesys Portal

  • Genesys Portal is your landing page for Business Edition Cloud applications. Genesys Portal provides single sign-on access for improved usability and seamless transition across all Genesys Cloud applications.

Single Sign-On

  • A user accessing the Genesys Portal services will do so through a single sign-on process. For example, if a user wishes to log into Agent Desktop and Platform Administration the user will sign in only once when accessing the first service and Genesys Portal will automatically sign the user into the other service. More services will be added to this single sign-on group of services in the future.

Known Issues

  • To log out of Genesys Portal and the applications that you logged into using SAML, you must log out of Portal and close the browser session where you logged in using SAML.
  • The horizontal scroll bar and some links on the top bar do not display if the browser window is re-sized to a width narrower than 960 pixels. (GH-365)
Comments or questions about this documentation? Contact us for support!