Bug 1262159

Summary: Evolution EWS Authentication Fails when using Gnome Online Accounts
Product: [Fedora] Fedora Reporter: Louis van Dyk <louis>
Component: evolution-ewsAssignee: Milan Crha <mcrha>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 23CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-11 06:08:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Louis van Dyk 2015-09-11 01:27:53 UTC
Description of problem:
(This started a few months back in Fedora 22) ...
When using Gnome Online Accounts credentials for Evolution EWS, the authentication fails because it looks at the WRONG server name.  In our case, it's using the INTERNAL server DNS name, from the Internet side.  However, if the account details are entered DIRECTLY into Evolution, the correct server is used, and Exchange can be accessed.

Version-Release number of selected component (if applicable):
evolution-3.17.91-1.fc23.x86_64
evolution-data-server-3.17.91-1.fc23.x86_64
evolution-ews-3.17.91-1.fc23.x86_64
evolution-help-3.17.91-1.fc23.noarch
gnome-online-accounts-3.17.91-1.fc23.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Fresh install of F23 and update patches.
2. Add Microsoft Exchange account to Gnome Online Accounts.
3. Open Evolution - it fails to connect immediately, showing the "Reconnect" button.  See the EWS_DEBUG below.  Note the server name is the INTERNALLY used one, not the one resolvable on the Internet.

Actual results:
[louis@localhost ~]$ EWS_DEBUG=2 evolution 
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

(evolution:3575): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version.

(evolution:3575): GLib-GObject-WARNING **: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version.

(evolution:3575): GLib-GObject-WARNING **: The property GtkSettings:gtk-toolbar-style is deprecated and shouldn't be used anymore. It will be removed in a future version.

(evolution:3575): GLib-GObject-WARNING **: The property GtkCellRendererPixbuf:stock-id is deprecated and shouldn't be used anymore. It will be removed in a future version.

(evolution:3575): GLib-GObject-WARNING **: The property GtkButton:xalign is deprecated and shouldn't be used anymore. It will be removed in a future version.

(evolution:3575): GLib-GObject-WARNING **: The property GtkWidget:margin-left is deprecated and shouldn't be used anymore. It will be removed in a future version.

(evolution:3575): GLib-GObject-WARNING **: The property GtkButton:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future version.
< HTTP/1.1 2 Error resolving 'exhs01.africa.enterprise.root': Name or service not known
< Soup-Debug-Timestamp: 1441933475
< Soup-Debug: ESoapMessage 0 (0x564b6b0b6460)
  
< HTTP/1.1 2 Error resolving 'exhs01.africa.enterprise.root': Name or service not known
< Soup-Debug-Timestamp: 1441933475
< Soup-Debug: ESoapMessage 0 (0x564b6b0b6910)
  
< HTTP/1.1 2 Error resolving 'exhs01.africa.enterprise.root': Name or service not known
< Soup-Debug-Timestamp: 1441933499
< Soup-Debug: ESoapMessage 0 (0x564b6b0b6460)
  

(evolution:3575): GLib-CRITICAL **: g_hash_table_destroy: assertion 'hash_table != NULL' failed
[louis@localhost ~]$ 


Expected results:
It should use the correct server name, and connect to Exchange.

Additional info:
This is also broken in Fedora 22.

Comment 1 Milan Crha 2015-09-11 06:08:21 UTC
Thanks for a bug report. This is most likely "caused" by the fix for [1]. I do not think it's any bug in the code, see the [1] for the rationale, this is more of the issue with the Exchange server's autodiscover setup, returning an internal address instead of an external.

An option to workaround the server settings issue (until the admins fix it) is to add the host into the /etc/hosts, redirecting the address to the public server.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=750427