cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
627
Views
0
Helpful
2
Replies

Unable to Add Authorization With OAuth 2.0 in WebEx

ravikumarmani93
Level 1
Level 1

Hi Team,

I'm trying to add authorization with WebEx Connect. I'm getting internal server error. It is not showing much. I have attached screenshot of error and my configuration for OAuth 2.0 type. I tried with same configuration through postman, all works fine. But, WebEx Authorization always failing. I'm trying for WebEx outbound webhook for push notification delivery receipts. Am I missing anything here? Please check the screenshot and let us know if any.

ravikumarmani93_0-1731514720596.png

ravikumarmani93_1-1731514877780.png

 

 

2 Replies 2

sandiban
Cisco Employee
Cisco Employee

Hello @ravikumarmani93,

Thanks for sharing the screenshot with the details to understand the situation better.
Actually you need to ask the developer who have designed this Portal to be able to generate the Access & Refresh token pair for better guidence on it. 
But I can find there are certain values which are not right for the certain request parameters as the screenshot provided.

Let's say the "clientId" and "clientSecret" - no way those are the valid Webex Integration client ID or, client Secret value.
You should be able to find these values in the Integration details page that you created in the Webex Developer Portal, under your Webex account. That should be corrected.
Basically you create the Webex Integration from here - https://developer.webex.com/my-apps/new and once the Integration is created, you should be able to find the these ClientId or, ClientSecret values there.

Next, while you're trying to generate the fresh Access Token - the Grant Type can never be "client credentials".
It must be set to "authorization_code". It's documented here as well - https://developer.webex.com/docs/integrations#getting-an-access-token 
And for the "Scopes", I'd say it'd be good if you could at least keep the scope value as "spark:all" there.

Also, the Access Token URL is also not correct, it should be - https://webexapis.com/v1/access_token 

I believe this Portal has been implemented following the POSTMAN Auth Type "OAuth 2.0" mechanism and that's why I'm sharing the Blog post we prepared for what value you should provide for which fields.
You can review this Blog Post once - https://developer.webex.com/blog/generating-an-oauth-token-pair-using-a-webex-integration

Hope this helps!
But in case of any further queries, please feel free to reach out to us.

Kind regards!
Sandip

Please Note: If you think the solution provided above was helpful and satisfactory, please accept it as a Solution! However if you want to discuss it further and get yourself unblocked, please don't hesitate to reply back on this thread and we'll try to answer those queries by the soonest. In that case, once all of your queries are cleared - finally you can mark it as "Accepted as Solution"

@sandiban Thanks for your response. We are using external provider OAuth for outbound webhook.

Ex: WebEx > Application

For sending delivery receipts of push notifications from Webex to Application, we have this setup. WebEx should authenticate using OAuth 2.0 to application for completing integration. That's where we have this internal server issue.