Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-80380

Fix Microsoft OAuth2 support - Scope & Endpoint

XMLWordPrintable

    • 6
    • Team Hedgehogs 2025 Sprint 2.2

      MDL-61921 added support for  XOAUTH2 for outgoing/incoming mail. However, this seems to not completely work work with O365.

      Based on initial investigation we found:

      We were to register a Business account of o365 and test it with Moodle.
      However, we are encountering an issue with our core_oauth2 codebase. When the admin attempts to connect the Micosoft OAuth2 to a system account, we encounter a problem. Our core_oauth2 currently only supports one entry point: https://graph.microsoft.com. Unfortunately, Microsoft is using https://outlook.office.com to grant the permission for the token.

      Additionally, when requesting the token and refresh-token, Outlook's entry point requires a "scope" parameter that is not needed in the Graph entry point.

      This tracker is to address this issue.

        1. verify 3.png
          verify 3.png
          24 kB
        2. verify 2.png
          verify 2.png
          46 kB
        3. verify 1.png
          verify 1.png
          27 kB
        4. result.png
          result.png
          317 kB

            huongn@moodle.com Huong Nguyen
            matt.porritt@moodle.com Matt Porritt
            Stevani Andolo Stevani Andolo
            David Woloszyn David Woloszyn
            Stevani Andolo Stevani Andolo
            Votes:
            3 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 week, 1 day, 2 hours, 14 minutes
                1w 1d 2h 14m

                  Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.