[V20 Bug] Google OAuth integration appends port 443 instead of 5001 (redirect_uri_mismatch)

Shap

Customer
Joined
Nov 12, 2023
Messages
5
Reaction score
3
Hi Community,

After updating to the latest 3CX build, I am encountering a redirect_uri_mismatch error when attempting to complete the Google Workspace / SSO integration setup.

In the 3CX Management Console under Google Workspace Integration, the interface explicitly states:

"You will need to copy this URI into the Authorized Redirect URI section in the Google Cloud Console: https://[YOUR_3CX_FQDN]:5001/oauth2google"
However, when clicking on Google login button to launch the Google OAuth flow, 3CX builds and sends an outbound authorization request with port 443 / no port explicitly defined:

redirect_uri=https://[YOUR_3CX<_FQDN]/oauth2google

Has anyone else noticed this discrepancy in the recent update, or is there a patch planned to align the generated URI string with the UI prompt?

Thanks!
 
Last edited:
Hi @Shap we are aware about this in sp10 alpha 2.

Could you please open a support ticket with us so we can apply a patch for you.

Thanks!
 
Last edited:
Hi @Alejandro_3CX,

Thank you for the quick reply.

To confirm my current port configuration shown on the dashboard:

  • HTTP: 5000
  • HTTPS: 5001
Under Integrations > Google, the callback URI displayed in the UI does indeed include port 5001 (https://[YOUR_3CX_FQDN]:5001/oauth2google).

Google SSO had been working seamlessly on this server since initial setup. The issue began immediately after updating to Version 20.0 Update 10 (Build 1621 Alpha - AI 1.6.57).

Upon inspecting the request payload sent when clicking the "Sign in with Google" button on the 3CX login page, the generated parameter drops the port:redirect_uri=https://[YOUR_3CX_FQDN]/oauth2google

Because the URL displayed in the Admin Console contains :5001 while the actual login page generates a request without :5001, Google Cloud rejects the request with Error 400: redirect_uri_mismatch.

Could this be a bug introduced in Build 1621 Alpha regarding how the OAuth redirect URL is constructed?
 
Hi @Shad, could you please open a support ticket with us to apply a patch on this system that will fix it.

Thanks!
 

Forum statistics

Threads
112,102
Messages
590,770
Members
165,087
Latest member
Amey Nhavelkar