Genesys Cloud - Developer Community!

 View Only

Sign Up

  • 1.  Syntax for Microsoft Entra ID provider parameter

    Posted 10-08-2025 16:09

    Given the following page: Genesys Cloud Developer Center

    In the description for the 'provider' parameter, it reads:

    Authentication provider to log in with. Valid values are "okta", "adfs", "salesforce", "onelogin", "gsuite", or "ping".

    My question is, what is the proper value syntax for Microsoft Entra ID? Is that also adfs? is it simply web noted Microsoft%20Entra%20ID? 

    Lil' help? 

    --C#


    #Integrations
    #PlatformAPI
    #PlatformSDK

    ------------------------------
    Chip Sharp
    n
    ------------------------------


  • 2.  RE: Syntax for Microsoft Entra ID provider parameter

    Posted 10-08-2025 17:08

    In the Single Sign-On config settings you can choose from a drop-down list of providers which includes Microsoft Entra ID

    Did you try entering that even though not listed in the Developer Center?



    ------------------------------
    George Ganahl GCCX-AI, GCP, GCSME
    Technical Adoption Champion
    Genesys
    2024 Community Member of the Year
    ------------------------------



  • 3.  RE: Syntax for Microsoft Entra ID provider parameter

    Posted 10-08-2025 18:12

    Hi George--

    I have the SSO provider correctly and successfully set up in the interface, but my question is more about how to I reference it in the code as prescribed by the documentation. It seems that the document is in need of updating now that this provider has been added to the interface options. So again, what is the <providername> value expected for the provider= parameter when using Microsoft Entra ID? (I tried it in web notation without success: Microsoft%20Entra%20ID)

    https://login.mypurecloud.com/oauth/authorize
    ?client_id=<my-client-id>
    &response_type=code
    &redirect_uri=<http://example.com/oauth/callback>
    &org=<orgname>
    &provider=<providername>
    &target=<orgid>
    &state=<uri%20encoded%20value>
    &prompt=login


    ------------------------------
    Chip Sharp
    n
    ------------------------------



  • 4.  RE: Syntax for Microsoft Entra ID provider parameter

    Posted 10-09-2025 03:50
    Edited by Jerome Saint-Marc 10-09-2025 03:51
    Hello,

    I am not from the Auth team and I do not have access to Microsoft Entra ID to create a proper SSO integration.
    But I did a quick test defining a fake Entra SSO integration in my org (just to get the tile in the GC Desktop login page and try the login url with the provider and org parameters).

    It seems that with the NEW SSO integrations, the provider value is the id of the identity provider in the Genesys configuration.
    I noticed this scrolling over the SSO integration (Entra) logo/icon in the Genesys Cloud Desktop login page (to see the url and what was after /providers/....).

    I assume it is because multiple SSO integrations from the same identity provider are now possible ( https://help.mypurecloud.com/articles/add-multiple-single-sign-on-providers-to-genesys-cloud/ ).
    Legacy SSO integrations (created before new endpoints were released) appear to still be using adfs, ...

    We've raised the question internally to get a confirmation and to ask for an update of the Developer Center page (if that's indeed the appropriate provider value). Many are out this week at an external event so it may take a while.
    But you can still try it and see if it does work for you.
    I'll update this post if I said something wrong, or dumb, or both... 🙂
    Regards,



    ------------------------------
    Jerome Saint-Marc
    Senior Development Support Engineer
    ------------------------------



  • 5.  RE: Syntax for Microsoft Entra ID provider parameter

    Posted 10-10-2025 01:19

    Just to confirm that's indeed the id of the identity provider (UUID) on new SSO integrations - to support multiple SSO configs (from same or different providers).

    Regards,



    ------------------------------
    Jerome Saint-Marc
    Senior Development Support Engineer
    ------------------------------