flavorjones / calendar-assistant

Command-line tool to manage your Google Calendar
Apache License 2.0
19 stars 5 forks source link

Exchange integration #151

Open gsiener opened 4 years ago

gsiener commented 4 years ago

Please fix this bug 😭

flavorjones commented 4 years ago

Hi, @gsiener. Thanks for raising this issue! @mikfreedman and I have already been talking about this, so let's use this issue to provide some visibility into our research and work.

flavorjones commented 4 years ago

Pinging @osis

flavorjones commented 4 years ago

@mikfreedman got a branch I can peek at / collaborate on?

mikfreedman commented 4 years ago

@flavorjones We're still figuring out what we need for a PoC of the Auth Flow. I have shared our scratch documents with you

osis commented 4 years ago

haven't forgotten about this. Mapped out the flow to get API access, this is what I'm thinking based off of the Microsoft docs...

< Calendar Assistant launches https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps >

1) Click on "New Registration" 2) Give it a name (ex. calendar-assistant) 3) Choose a scope 4) Redirect URL should be "https://login.microsoftonline.com/common/oauth2/nativeclient" 5) Click "Register" 6) Click on the new application 7) Paste Client ID

This would allow the code to kick off an oauth flow and grab access/refresh tokens. Does that sound about right?