<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00007KAaxGCATOkta Identity EngineWorkflowsAnswered2024-01-16T18:34:20.000Z2021-12-10T00:45:38.000Z2021-12-10T18:04:22.000Z

BrianC.37067 (Service Corporation International) asked a question.

Okta Workflow API connector using oAuth to connect to Webex

I am trying to create a API connector in Workflows to connect to Webex so that I can have the ability to send a message to Webex teams.

Their API uses OAuth. I have created an integration and was issued a client id, secret and I selected a scope. Based on the entries on the "new connector" screen this should be straightforward, but I am not getting all the way through the process. I am following the guidance from Webex's site (https://developer.webex.com/docs/integrations).

I have filled in the form as follows (client id and secret have been altered)

/help/servlet/rtaImage?refid=0EM4z0000028pU2

This returns an error from Webex. The error message is encoded in the URL:

https://idbroker.webex.com/idb/oauth2/oauth2Error.jsp?error=invalid_request&error_description=Missing%20parameters%3A%20client_id%20&state=sci_okta_workflow

 

So I specify the client id in the URL and I got an Okta Workflow page, so I added the redirect uti to the authorize path, then I had to add the scope. That seemed to be enough because after that I received this page when I clicked "create":

/help/servlet/rtaImage?refid=0EM4z0000028pU7

The URL is https://oauth.workflows.oktapreview.com/oauth/httpfunctions/cb?code=MjVkYTM0MTgtNjE5My00Y2M2LWE5MDUtYWRjMzczNDQ3YmY4M2VlMTQ3MWItODgw_PF84_8d80b358-63ce-4216-8f53-875afd41267d&state=sci_okta_workflow

So no clue there as to what went wrong.

 

I am assuming that Workflows is trying to exchange the code for an authorization token and it is failing, but I do not know how to see what is going on.

 

If there are other parameters that need to be passed, I would have assumed that Okta supplied them from the values in the client ID, secret and scope fields. I also assume that the redirect url is supplied as it is fixed, but apparently not.

 

Other things I have tried. On the Access Token Path, I have specified a grant type of "authorization_code" and I have tried "refresh_token"


This question is closed.
Loading
Okta Workflow API connector using oAuth to connect to Webex