Genesys Cloud - Main

 View Only

Sign Up

  • 1.  Configuring Entra ID for Single Sign on

    Posted 7 hours ago

    Hi, 

    We have configured Entra ID as Single Sign on in our Org & noticing the landing page through Entra is different to our existing SSO - Ping Identity & we would like to provide the same experience for users.

    Entra: 

    Through Entra, user is navigated to https://login.mypurecloud.com.au/#/splash & asked to choose option - for Agent they have to click on Communicate/Collaborate to login. 

    Ping (Existing): 

    It will directly land user on https://apps.mypurecloud.com.au/directory/#/person-v2/(User UID)

    SAML Attributes used for Entra: 

    • givenname user.givenname
    • surname user.surname
    • emailaddress user.mail
    • name user.userprincipalname
    • Email user.userprincipalname
    • Uniquie User Identifier user.userprincipalname

    If someone has gone through similar issue, can you please help us on how this has been resolved?


    #API/Integrations

    ------------------------------
    Radha Madduri
    Platform Test Engineer
    ------------------------------


  • 2.  RE: Configuring Entra ID for Single Sign on

    Posted 4 hours ago

    Hi Radha 

    -

    I've done some research here, see if it helps, but I confess I'm not sure if it makes sense.
    I've done implementations with Azure, Google, and Salesforce, but never with ENTRA and PING, and this has never happened with me 
    -
    Response Orcherstrator IA: 
    -

    What you are seeing is typically related to the entry URL used by the IdP-initiated login, not the SAML attributes themselves.

    When the authentication flow starts through the Genesys login domain (for example login.mypurecloud.com.au), the user is first redirected to the Genesys splash page, where they must choose between options like Communicate or Collaborate. This behavior is expected when the login process lands on the generic login endpoint.

    However, if the user lands directly on an application URL such as:

    

    

    

    

    

    

    

    

    

    

    

    

    

    https://apps.mypurecloud.com.au/directory/...

    Genesys Cloud bypasses the splash page and opens the application directly after SSO authentication.

    This is likely why your Ping Identity configuration lands users directly inside the app, while the Entra flow sends them to /splash.

    To provide the same experience, you typically need to:

    • Configure the IdP-initiated login URL in Entra to target the Genesys application URL instead of the generic login page, or
    • Ensure the RelayState / application launch URL points to the desired Genesys Cloud application (e.g., /directory or /clientapp).

    The SAML attributes you listed (givenname, surname, email, etc.) are standard and should not affect the landing page behavior.

    Genesys Cloud's login service will redirect users to the splash page when the authentication originates from the generic login endpoint rather than a specific app URL.



    ------------------------------
    Kaio Oliveira
    GCP - GCQM - GCS - GCA - GCD - GCO - GPE & GPR - GCWM

    PS.: I apologize if there are any mistakes in my English; my primary language is Portuguese-Br.
    ------------------------------

    Original Message


Related Content