RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1885229 - Allow change of the Microsoft 365 OAuth2 endpoints
Summary: Allow change of the Microsoft 365 OAuth2 endpoints
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: evolution-ews
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Milan Crha
QA Contact: Michal Odehnal
URL:
Whiteboard:
Depends On: 1886026
Blocks: 1887925
TreeView+ depends on / blocked
 
Reported: 2020-10-05 13:30 UTC by Andrew Mike
Modified: 2024-10-01 16:56 UTC (History)
8 users (show)

Fixed In Version: evolution-ews-3.28.5-10.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1887925 (view as bug list)
Environment:
Last Closed: 2021-05-18 15:19:09 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME evolution-ews issues 121 0 None None None 2020-10-05 13:30:52 UTC

Description Andrew Mike 2020-10-05 13:30:52 UTC 
1. Proposed title of this feature request  
Detect Microsoft 365 non-worldwide cloud endpoints
  
3. What is the nature and description of the request?
Currently, Evolution's OAuth support for Microsoft 365 is hard-coded to look at only one endpoint (outlook.office365.com). Certain other cloud tenancies for Microsoft 365 have other endpoints that a customer might need to access (see https://docs.microsoft.com/en-us/microsoft-365/enterprise/microsoft-365-endpoints?view=o365-worldwide).
  
4. Why does the customer need this? (List the business requirements here)
Customer is a consumer of the US Goverment GCC High endpoint and requires e-mails to be digitally signed and/or encrypted in order to comply with DoD regulations. Microsoft 365 users cannot send signed or encrypted e-mail using the Outlook Web App in a web browser under Linux. Also note that Microsoft 365 GCC High does not support IMAP. The only option for signed/encrypted email under Red Hat Enterprise Linux is to use Evolution to connect to Microsoft 365 GCC High.  
  
5. How would the customer like to achieve this? (List the functional requirements here)
Customer would like functionality to be implemented to be able to use the OAuth backend for Microsoft 365 with non-worldwide cloud endpoints, either through manual selection or automatic detection.
  
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  
Evolution can successfully configure an email/calendar Office365 account using the US Government GCC High endpoint (outlook.office365.us).
  
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
This RFE was filed upstream at <https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/121>.
  
9. Is the sales team involved in this request and do they have any additional input? 
Sales is not involved.
  
10. List any affected packages or components.  
evolution
Comment 3 Milan Crha 2020-10-05 16:59:56 UTC 
Thanks for a bug report. Let's move this to evolution-ews, where the code is. I already talk tot he reporter of the upstream bug, waiting for some information. "The worst" case would be to allow manual setting for now, possibly through gsettings. I might come with something more user friendly upstream, hopefully. The thing is that users will be able to connect to a Microsoft 365 site only with OAuth2 soon (this month), which will make the user sof the other than outlook.office365.com users out of the ability to connect (they could/can not use the OAuth2).
Comment 4 Milan Crha 2020-10-06 17:39:02 UTC 
I just provided a patch upstream [1], which can be backported to RHEL. I'm only waiting for a confirmation from the upstream reporter that the things work as expected in the non-WorldWide environment. I also updated the documentation about the OAuth2 setup for the Exchange EWS [2] (that's referenced also from the tab when creating the account).

[1] https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/121#note_927543
[2] https://wiki.gnome.org/Apps/Evolution/EWS/OAuth2
Comment 6 Milan Crha 2020-10-07 12:44:24 UTC 
I received a confirmation from the upstream reported and commit the change (slightly modified) to the sources [3] for 3.39.1+. It can be backported with not much effort.

[1] https://gitlab.gnome.org/GNOME/evolution-ews/-/commit/b3f7d5817952e600d9bba29b955d4cd135b3ee46
Comment 11 Michal Odehnal 2020-10-19 11:02:06 UTC 
Unable to reproduce with evolution-ews-3.28.5-10.el8.x86_64. Switching to VERIFIED.
Comment 12 Michal Odehnal 2020-10-19 11:03:33 UTC 
Well, that was not a helpful comment, its more like: I am able to change Microsoft 365 OAuth2 endpoints with evolution-ews-3.28.5-10.el8.x86_64
Comment 14 errata-xmlrpc 2021-05-18 15:19:09 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Low: evolution security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1752
Note You need to log in before you can comment on or make changes to this bug.