Re: [Evolution] evolution ews cannot follow our autodiscovery

On Tue, 2019-07-02 at 11:16 +0000, Joakim Tjernlund wrote:
Does this <Action>redirectAddr</Action> address make sense
to Evolution?

no, evolution-ews doesn't know about it. It would work fine if a
standard redirect response had been made by the server, the one through
the HTTP response code and such. It seems it might not be possible in
this case, as it changes the user name too. The RedirectAddr element
does that at least, according to [1]. And this [2] link shows what the
Action values can be.

You can rerun your script with
host name and user as returned by the server, which should give you the
desired settings. You can copy the ASUrl content into the Host URL and
the OABUrl content into the OAB URL in Evolution, if they are present.
You can get multiple addresses for each, some may work only from the
company network, some can be accessible also from the public addresses.

On Tue, 2019-07-02 at 11:30 +0000, Joakim Tjernlund wrote:
futhermore I notice that
- plain http requests are just redirected to https
- I never get an user/passwd prompt when I do fetch URL in Evo

It looks like the credentials had been read from the libsecret/gnome-
keyring. I see a request for "SoupMessage 1 (0x7fd8c86c1e50)", but not
its response (after the 401 response, which means that the server asked
for the credentials). It looks like you didn't receive the
"redirectAddr" within evolution-ews for some reason, or you didn't wait
long enough to have it included in the log. The next time, try to not
expose the whole log, remove the private information and the
information you cannot decipher (like the encoded bits).

This looks like a very specific case, but if you are willing to help to
test any changes, then feel free to open a new bug against evolution-ews
at [3] and we can follow there.
        Thanks and bye,


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]