Open detrout opened 5 years ago
Just more about my experiences with office365 with the ews resource using oauth.
After a while (few hours? after sleeping laptop?) I get a message saying that I need to authenticate, but I didn't see any obvious way of going through the login screen again.
I finally found a work around by going into akonadiconsole and reconfiguring the resource, hitting "try connection" and that gave me the webui login screen.
Also after a while it hangs (though... probably after I had gotten a "you need to log in" prompt.) and I needed to restart kontact (after logging in) in order for it to start finding office365 mail again.
Hope this "my experiences trying this" is helpful in some way.
Hi,
I made some progress getting the ews resource with to compile with oauth2 support. Though I had some problems configuring the resource. (This is using the 5.12 version)
I tried configuring through Kontact add custom resource a few times and though the oauth web dialog popped up the OK button never was enabled. I also had to manually provide the office 365 exchange endpoint "https://outlook.office365.com/EWS/Exchange.asmx" I wonder if you pick the office365 radio button in the authentication section of the configuration page if the resource should suggest the default office365 endpoint?
I was able to configure the resource through akonadiconsole, it took a couple of tries through the oauth login screens before the it took but eventually it succeeded. (Did I fail typing my password? Was I just too impatient? I don't know)
During the initial download of messages I saw this message frequently in the kontact log, I was wondering if you knew if it was an issue.?
Also i was wondering if that's why I wasn't able to view or delete messages during the initial download. But apparently it was just the resource was busy downloading and didn't have the time or connections to handle my request. Eventually it made enough progress I was able to delete and read messages.
I'll put a pull request together with the unpleasant hacks I tried to get kdepim-runtime to link to Qt5NetworkAuth.
(Also office365 supports SPENEGO, and that didn't seem to be an allowed SASL option. That seems like it could be another issue.)