On Thu, 2021-09-02 at 18:01 +0200, Vincent Hennebert via evolution-list
wrote:
> It looks like Evo is ignoring the content returned by
> the last SSO URL, but of course I may be wrong.
Hi,
evo reads the returned auth code from the redirect URI and then asks
the server (by other channel) for the token. Just like DavMail or any
other. The token is received from the "/oauth2/token", which is the
place the office365.com rejects the data on your side.
> After that I see a connection to
> https://login.microsoftonline.com/common/oauth2/nativeclient
That's the application's redirect URI. The evo-ews uses it too, as its
default. You've got past this place, it's done before the
"/oauth2/token".
If you can see what DavMail sends to the "/oauth2/token", then compare
it with what evo-ews sends. Maybe they use special scopes or something.
Do you see in the DavMail logs also the "/oauth2/authorize" call?
I'm really out of idea, I'm sorry.
Bye,
Milan
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
