Heinz Wrobel

I have forward ported my 6.0.1 patches for the client_credentials flow yesterday as I need to also switch to Graph use. In our corporate environment with that flow, scopes do not show up. Another topic is that Graph /me requests cannot be done in that flow. You always need to have a valid /users/ spec, which affects how the requests are built. While it seems to work well now, I am still in prototype phase for the forward port and need to go through corporate red tape before I could formally provide...

O365Token.java/setJsonToken fails because of bad scope handling

Turns out that I had to implement against what our corporate IT permitted and configured on the Exchange side for the specific case I had of a 24x7 application serving a single account. I have neither control nor visibility of the infrastructure end. This is why this patch set specifically implements the client_credentials flow based on app-only. The code may be at least partially useful for support of delegated authentication, but I had no means to even consider that. Yes, this only works if the...

Support of O365 client_credentials authorization flow

Hi, As part of a company internal project I have developed a handful of patches that implement the client_credentials authorization flow with Exchange on top of DavMail 6.0.1. The changes tweak authentication handling while staying backwards compatible and also update the [english] GUI to select the necessary Oauth settings without hacking into the configuration. They enable EWS+Oauth2 for the non-interactive use case of service/server style applications that need to run email 24x7 on specific accounts...