Auth token response URL does not appear

[hbarel]

I am not sure it's an issue with Davmail, but I would appreciate any help I can get nevertheless.

I use O365Manual mode, and send it to login and get a RefreshToken. If I do not specify a client-id, then I do not get to the 2FA screen at all, which is not surprising. If I use the client-id that the browser uses when logging in, then I do get the 2FA screen and can authenticate. However, this client-id value requires setting the redirect-uri to be that of ...landingV2. When I set redirect-uri to that ...langingV2 page, logging-in succeeds, but I get straight to the O365 portal after logging in, and not to that blank page where the URL line contains the material for the token.

Is there a way for me to get to that blank-screen? If not, is there a way to scrape the token from the page and enter it into Davmail manually?

[mguessan]

Both client-id and redirect-uri are mandatory, you can use the default DavMail provided values or a client id authorized by O365 tenant admins. For Outlook Desktop values are: client_id: d3590ed6-52b3-4102-aeff-aad2292ab01c redirect_uri: urn:ietf:wg:oauth:2.0:oob

The issue is that urn: is not a protocol supported by desktop browsers. Thus you may get a prompt "Are you trying to sign in to Microsoft Office?"

In this case open dev tools in the browser with F12 and display network tab, when you click continue you should see a new HTTP request, the response is a redirect with a Location header with the code you are looking for.

[rsekman]

Thank you for this information.I think both the values you've given and what to do about the no-op "Are you trying to sign in…" would be good to include in documentation / on the web site.I was not able to get davmail to work until downgrading to specifically Oracle Java 8, and this would have saved me a lot of time. The issue was O365Interactive would not work with other Javas because of missing JavaFX (even though the library was installed). Is this a known issue?On 16 Nov 2022, at 12:04, Mickaël Guessant @.***> wrote: Both client-id and redirect-uri are mandatory, you can use the default DavMail provided values or a client id authorized by O365 tenant admins. For Outlook Desktop values are: client_id: d3590ed6-52b3-4102-aeff-aad2292ab01c redirect_uri: urn:ietf:wg:oauth:2.0:oob The issue is that urn: is not a protocol supported by desktop browsers. Thus you may get a prompt "Are you trying to sign in to Microsoft Office?" In this case open dev tools in the browser with F12 and display network tab, when you click continue you should see a new HTTP request, the response is a redirect with a Location header with the code you are looking for.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

[hbarel]

In this case open dev tools in the browser with F12 and display network tab, when you click continue you should see a new HTTP request, the response is a redirect with a Location header with the code you are looking for.

Thank you. I did not get to try this method, but instead, I logged-in manually (as I usually do), and collected the "code=..." redirect URL before redirection actually happens into "landingV2". I ran Davmail and when it asked for the response to the challenge URL, I entered a crafted URL with the "code..." that I collected.

In return, I got the unhelpful response: "Device is not in required device state: domain_joined." I guess this is conditional access that does not allow Davmail, which apparently is distinguishable from the web-UI.

I wonder if I should give up...

[DeastinY]

Both client-id and redirect-uri are mandatory, you can use the default DavMail provided values or a client id authorized by O365 tenant admins. For Outlook Desktop values are: client_id: d3590ed6-52b3-4102-aeff-aad2292ab01c redirect_uri: urn:ietf:wg:oauth:2.0:oob

The issue is that urn: is not a protocol supported by desktop browsers. Thus you may get a prompt "Are you trying to sign in to Microsoft Office?"

In this case open dev tools in the browser with F12 and display network tab, when you click continue you should see a new HTTP request, the response is a redirect with a Location header with the code you are looking for.

I had the same issue and this finally worked for me. Thanks so much!