GNOME Bugzilla – Bug 338461
HTTPS not supported for OWA access
Last modified: 2008-08-06 08:26:15 UTC
Distribution: Fedora Core release 5 (Bordeaux) Package: Connector Severity: major Version: GNOME2.14.0 2.6.0 Gnome-Distributor: Red Hat, Inc Synopsis: HTTPS not supported for OWA access Bugzilla-Product: Connector Bugzilla-Component: Connector Bugzilla-Version: 2.6.0 Description: Description of Problem: If you specify a URL with https:// protocol in order to get access to OWA, it is rejected. Steps to reproduce the problem: 1. 2. 3. Actual Results: Don't get access to Exchange Expected Results: Should work as it would be http protocol How often does this happen? Every time Additional Information: ------- Bug created by bug-buddy at 2006-04-14 12:25 -------
https, support is there in connector and it works. What excatly is the error you are getting when you try to create an account? Are you able to access your account with same username and URLs, using Outlook Web Access (OWA)?
Here is the exact message, I'm getting: Could not configure Exchange account because an unkown error occured. Check the URL, userbale, and password, and try again. If I take firefox and the url is like https://xxxxxx/exchange , I'm getting connected
hmm.. "unkown error" Can you get the E2K_DEBUG traces for Evolution while configuring the account? Set E2K_DEBUG=4, and paste the traces here? See http://gnome.org/projects/evolution/bugs.shtml for more details.
Patrick: r u connecting exchange server thru proxy server ? if yes does that proxy server require authentication. There is no issue with SSL connection, this bug might be related to the type of exchange server setup.
After investigation, I understood that the company has setup the OWA on the rpc-over-http protocol and a Digital Certificate as to be used to established the connection. This is why it works under Firefox and not with Evolution, since I guess that rpc-over-http protocol is not supported/nor implemented (again Microsoft standard)
RPC-over-HTTP and OWA are two different things. However, I think I have run into the same bug as you have. The OWA you are connecting to requires a client certificate to authenticate you to the proxy. It looks like the exchange-data-connector might not implement the correct calls with libsoup to load this client certificate up. Perhaps there would be a way to access Evolution's certificates to find a certificate that can act as an SSL Client certificate and use that.
This is probably a duplicate of #273869
*** This bug has been marked as a duplicate of 273869 ***