Bug 430537 - Cannot add EWS server
Summary: Cannot add EWS server
Status: REPORTED
Alias: None
Product: kontact
Classification: Applications
Component: mail (show other bugs)
Version: 5.16.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-18 11:05 UTC by Aaron Williams
Modified: 2023-09-04 12:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Williams 2020-12-18 11:05:00 UTC
SUMMARY

I have an account with office365 with 

STEPS TO REPRODUCE
1. Add a new custom receiving account
2. Allow access to KWallet5
3. Choose EWS
4. Fill in Email
5. Select OAuth2 (Office 365)
6. Turn off Server Autodiscovery
7. Enter https://outlook.office365.com/EWS/Exchange.asmx
8. Click Try Connect
9. Fill in the OAuth2 page (successful)
10. Status reports OK.
11. OK button remains greyed out. No way to add the account.

OBSERVED RESULT
OK button remains greyed out

EXPECTED RESULT
I expect to be able to click OK.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Aaron Williams 2020-12-18 11:23:37 UTC
Here are the Akonadi logs:
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x563436f861c0) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x563436f861c0) identified as "AgentBaseChangeRecorder - 94445167940208"
org.kde.pim.ews: Authentication failed:  Password request failed
kf.kio.core: Invalid URL: QUrl("")
org.kde.pim.ews.client: Failed to process EWS request: Access to restricted port in POST denied.
ERROR "Failed to process EWS request: Access to restricted port in POST denied."
Please register the custom scheme 'urn' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler.
org.kde.pim.ews.client: Starting OAuth2 authentication
org.kde.pim.ews.client: Launching browser for authentication
org.kde.pim.ews.client: PKeyAuth certificates not found
kf.kio.core: Invalid URL: QUrl("")
org.kde.pim.ews.client: Failed to process EWS request: Access to restricted port in POST denied.
ERROR "Failed to process EWS request: Access to restricted port in POST denied."
js: A cookie associated with a cross-site resource at https://login.microsoftonline.com/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
js: A cookie associated with a cross-site resource at https://login.live.com/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
org.kde.pim.ews.client: Authentication succeeded
Comment 2 Marco Schmidlin 2023-09-04 12:45:04 UTC
Happens to me on Kubuntu 23.04. Is there any more details that needs to be provided? Seeing that there are major changes on the way for KF6, will those address the several issues for Office365 support?