|
From: Bence F. <be...@fe...> - 2022-12-28 20:07:25
|
On Mon Dec 26, 2022 at 16:52, H wrote: > On December 26, 2022 2:39:56 AM EST, Bence Ferdinandy <be...@fe...> wrote: > >2022. dec. 26. 3:08:32 H <ag...@me...>: > > > >> The TENANT_ID is available on the portal.azure.com page when logged > >in, > >> registering an app to get the CLIENT_ID is locked down. I don't see > >any > >> upside for the organization to provide a CLIENT_ID, only a potential > >> security risk, so I do not see that happening. > > > >For the client id, I suggest you use this: > >https://github.com/ferdinandyb/dotfiles/blob/master/.config/emailconfiguration/mutt_oauth2.py#L77 > > > >you will find that it's a rather well known application and thus will > >likely be already authorized. > > > >Besr, > >Bence > > Thank you. Does this require someone has already gotten mutt registered as an application on my organization's O365 site? No, it's actually Thunderbird that needs to be authorized, but it usually is. Best, Bence -- +36305425054 bence.ferdinandy.com |