08-05-2025 05:11 AM - edited 08-05-2025 05:12 AM
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
Solved! Go to Solution.
08-06-2025 12:50 AM
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:
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.
08-06-2025 12:50 AM
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:
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.
08-06-2025 12:12 AM
Could be a token refresh issue have you tried fully disconnecting and reconnecting the Webex integration?
08-06-2025 12:43 AM
I deleted the integration and created form scratch - same issue.
08-05-2025 08:01 AM
@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 .
08-06-2025 12:10 AM
Thank you ! You are right, wrong wording, authorization code. I will contact support in that case.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide