Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-5579

Oauth2 Google for outgoing mail does not request a Redirect URL

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.12.3
    • Fix Version/s: 5.13.0-b2
    • Component/s: Staff Interface
    • Labels:
      None

      Description

      When selecting Oauth2 for Google under /admin/settings/company/emails/mail/ for outgoing mail, we seem to be missing a Redirect URL, required by Google (Is this also required by Microsoft or no?)

      As a result, Google returns the error: Error 400: redirect_uri_mismatch

      ALSO check the Support Manager, when selecting Google for OAuth 2.0 on a department there is also no Redirect URL.

        Activity

        Hide
        jonathan Jonathan Reissmueller added a comment -

        This is set automatically in the backend. It is used to redirect to the settings page after authorizing. But it relies on the company hostname so if that doesn't match the installation that would cause an issue.

        Show
        jonathan Jonathan Reissmueller added a comment - This is set automatically in the backend. It is used to redirect to the settings page after authorizing. But it relies on the company hostname so if that doesn't match the installation that would cause an issue.
        Hide
        jonathan Jonathan Reissmueller added a comment -

        We mostly need to fix this in the back end to use something more reliable than the hostname company setting. Also let's display the uri in a readonly field to help debug if people have issues.

        Show
        jonathan Jonathan Reissmueller added a comment - We mostly need to fix this in the back end to use something more reliable than the hostname company setting. Also let's display the uri in a readonly field to help debug if people have issues.

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              18/Dec/25

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 22 minutes
              22m

                Agile