Summary: | Unable to define Custom Oauth2 Settings | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Jonas Andradas <j.andradas> |
Component: | EWS Resource | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | j.andradas, krissn, me |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Jonas Andradas
2021-09-08 15:00:58 UTC
Sorry, forgot to add the URL to Chriss' blog [1] from where I got the Oauth2AppId setting name: [1] https://micreabog.wordpress.com/2017/10/05/akonadi-ews-resource-now-part-of-kde-pim/ Hi Jonas, I have exactly the same issue as you. My organization only allows Evolution EWS. Here is how I changed the value of the Oauth2AppId usign qdbus: qdbus org.freedesktop.Akonadi.Resource.akonadi_ews_resource_0 /Settings org.kde.Akonadi.Ews.Settings.setOAuth2AppId "751cf8be-ca07-484b-9308-fac4b9d85eff" However, it did not work, because not only they check the app id but also how the app responses and if it not as expected, you will not be able to log in. In my case I got the following error: AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application: '751cf8be-ca07-484b-9308-fac4b9d85eff'. Try with the Outlook's appid. In my case, that didn't do the trick either. Hope you are more lucky than me. Hi Iyán, thank you for your comments. I have tried changing this using qdbus as per your suggestions. I have managed to change both the oAuthAppId and oAuth2ReturnURI with qdbus org.freedesktop.Akonadi.Resource.akonadi_ews_resource_10 /Settings org.kde.Akonadi.Ews.Settings.oAuth2AppId "d3590ed6-52b3-4102-aeff-aad2292ab01c" qdbus org.freedesktop.Akonadi.Resource.akonadi_ews_resource_10 /Settings org.kde.Akonadi.Ews.Settings.setOAuth2ReturnUri urn:ietf:wg:oauth:2.0:oob These settings are changed fine, but when I try to authenticate, I am taken through the journey just as before, so still not able to use Kmail here :( When access is not allowed because the device is not "configured properly", this is what I get from EWS in the error: App name: App id: 00000000-0000-0000-0000-000000000000 IP address: <REDACTED> Device identifier: Not available Device platform: Android Device state: Unregistered So, despite setting the Custom UserAgent to Microsoft Office 2016, and the OAuth2 App id to Outlook's, it seems that, for some reason, these are not being properly sent to EWS, or at least not in the way the server expects them. |