topic webex integration - authentication issues recently in Webex for Developers

webex integration - authentication issues recently

dbednarc — Tue, 05 Aug 2025 12:12:48 GMT

Hi Team,

I have a simple script that was working before basing on webex integration , that was pulling contents of webex spaces that I pointend.

Today I tried to do the authetnication to get the token, but I dont see the token any more in redirect url

I was pasting before contents of (1) and it was working

now I am getting :

https://www.google.com/?state=set_state_here

before I had token in this url , what changed?

how to fix that?

I tried to delete the integration and create a new one - same effect

Re: webex integration - authentication issues recently

Janos Benyovszki — Tue, 05 Aug 2025 15:01:48 GMT

@dbednarc note, that access tokens were never shared in OAuth URLs, what you might be confusing it with is the authorization code that you can exchange for an access token using the APIs. Here is the whole flow for reference https://developer.webex.com/create/docs/authentication.
In case you do not get the authorization code like this

http://your-server.com/auth?code=YjAzYzgyNDYtZTE3YS00OWZkLTg2YTgtNDc3Zjg4YzFiZDlkNTRlN2FhMjMtYzUz as described here https://developer.webex.com/create/docs/authentication#getting-an-access-token , then please open a support case with our team here - https://developer.webex.com/explore/support .

Re: webex integration - authentication issues recently

dbednarc — Wed, 06 Aug 2025 07:10:04 GMT

Thank you ! You are right, wrong wording, authorization code. I will contact support in that case.

Re: webex integration - authentication issues recently

Chloeharper — Wed, 06 Aug 2025 07:12:36 GMT

Could be a token refresh issue have you tried fully disconnecting and reconnecting the Webex integration?

Re: webex integration - authentication issues recently

dbednarc — Wed, 06 Aug 2025 07:43:59 GMT

I deleted the integration and created form scratch - same issue.

Re: webex integration - authentication issues recently

dbednarc — Wed, 06 Aug 2025 07:50:27 GMT

Issue solved by Support :

"""

After a quick test, it appears the issue stems from the redirect URL. The URL https://www.google.pl redirects to https://www.google.com, which prevents the authorization code from appearing in the redirected URL. When I changed the redirect URL to https://www.google.com, I was able to successfully receive the code in the URL as shown below:

https://www.google.com/?code=OGY0NzBlY2UtOTUwMi00NTYzLTgwNGEtOGRjNjI1ZTgwMWE3YmQ0MDU5NzEt[REDACTED_PORTION]&state=set_state_here

When using a redirect URL like https://www.google.pl that internally redirects to https://www.google.com, the OAuth flow may fail to capture the authorization code properly because the final redirected URL does not match the originally registered redirect URI. Changing the redirect URL to the exact final destination, such as https://www.google.com, ensures that the authorization code is correctly appended to the URL and received by your application.

Is there any specific reason for using https://www.google.pl instead of https://www.google.com ?
"""

After changing the url to google.com insted of google.pl it works.