SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** The EWS add-on is broken on office365.com using OAuth2 STEPS TO REPRODUCE 1. Create a calendar account of type "EWS" in KOrganizer 2. Enter an outlook.com mail address, select OAuth2 authentication, and provide office365.com as the EWS URL 3. Click "Try connect" button and provide my account credentials OBSERVED RESULT On first login attempt, login.live.com complained: "AADSTS165000: Invalid Request: The user session context is missing. One or more of the user context values (cookies; form fields; headers) were not supplied, every request must include these values and maintain them across a complete single user flow. The request did not return all of the form fields. Failure Reasons:[Missing session context cookie;Token is invalid;]", and login failed with KOrganizer reporting "Failed to process EWS request HTTP 401". On a subsequent second attempt, only KOrganizer reported HTTP 401. Closed KOrganizer and tried again, the above situation reappears. EXPECTED RESULT I should have my calendar set up and working SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Leap 15.3/Linux 5.3.18-150300.59.49-default #1 SMP Mon Feb 7 14:40:20 UTC 2022 (77d9d02) x86_64 (available in About System) KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.76.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION
Can only successfully add account by manually inputting email and password (or app password if you use 2fa) and also tryng to connect by manually putting in the office365 exchange URL. But even so, task lists do show up but they are empty inside. Cannot immediately confirm if calendar data loads or not.
it would be nice if someone could test this bug with newer KOrganizer versions (like 6.3.0 or above) and also with Frameworks 6.12
Krzysztof, do you think we can resolve this one?
The message from the OAuth2 server seems to indicate some missing cookies. Unless it is misleading, which I have sometimes seen in the past, it would indicate, that QWebEngine somehow lost cookies during the authentication flow. Hard to tell what this could have been. Some non-standard OAuth2 flow? I know that there is an option for organizations to customize the UI for the authentication flow. I can try to reproduce with the accounts that I have access to, but otherwise without logs this will be impossible to debug.
ok then. since this one is 3 years old now and there's been no reply to my comment since 2 weeks => I'll close feel free to re-open if this still happens