Create Oauth2 Athorization token without login screen

[Magudeeswaran_N]

Hi team,

I would like to know how we can create Ouath 2 athorization token without login screen. Because I am using /api/v2/conversations/calls/{conversationId}/participants/{participantId}/consult
API for making calls on hold. But this API requires Oauth2 acess token. I got to know that SAML2.0 type will provide us the access token without login screen but it requires SSO setup. But out client don't have anything like that. So kindly help me out.

Thanks

[tim.smith]

The only grant types that allow you authorize an application without using the Genesys Cloud login screen are the SAML2 Bearer and Client Credential grants. Only the former provides a user context, which is required for certain tasks, such as manipulating conversations.

[Magudeeswaran_N]

Hi tim,

Thanks for your information.
Is there any way we can call Oauth 2 API's in Data action. If so, how athorization will happen in that case. Will it open new login page.

Thanks,
Magu

[tim.smith]

@Magudeeswaran_N

Is there any way we can call Oauth 2 API's in Data action

Yes, data actions can make API requests to Genesys Cloud. OAuth 2.0 is the only supported authorization method for the Genesys Cloud Platform API. Data action configuration is documented here: About the Genesys Cloud data actions integration - Genesys Cloud Resource Center

But keep in mind that data actions only support the client credentials OAuth grant type, so you can't use data actions with API endpoints that require a user context.

[Magudeeswaran_N]

Hi tim,

I came across this blog

oAUTH 2.0 implementation

HI Alok, Check out these two pages for information on how to setup actions that use custom OAuth authentication. Once you select the oauth credential type, you'll configure an "auth action" that performs the authentication to get your token. Then you reference the output of the auth action in your regular action. Those articles go into more details to help you get setup. Let us know if you run into any problems. -Chris

where they mentioned about configuring Oauth 2 in data action. Is this valid way to do it, or we can't do this way.

Thanks,
Magu

[tim.smith]

@Magudeeswaran_N please take note of the next two replies in that thread:

oAUTH 2.0 implementation

Edit: see Tim's reply below - auth code grant does require a browser redirect as noted below, so client credentials is required. Hi Alok, I've only used data action Oauth with client credentials grant (client id / client secret): I don't believe the authorization code flow is supported directly, but you should be able to accomplish it with two "hand rolled" secure actions as long as the auth code is returned in the body of a JSON response. Since there is no user or interactive session, flows…

oAUTH 2.0 implementation

You can only use client credentials in data actions. None of the other grant types make sense in that context because data actions don't interact with the user's browser and therefore have no way to authenticate a user. If you need to make user-based API calls, you need to write a custom app to handle authentication and then make the API calls. That could take the form of a custom web page embedded in an agent script.

I'm saying the same thing now as I said then: You can only use client credentials in data actions. You cannot use user-based API endpoints in data actions.