On Mon, Jun 24, 2024 at 01:59:45PM -0700, Will Yardley <mutt-us...@veggiechinese.net> wrote: > Creating an app password, if you're allowed to by organization policy, > is going to be by far the simplest option, I think.
I wouldn't trust static app passwords, nor would I trust our security group if they allowed it, but I'm pretty sure they don't. > That said, if you're able to get the XOAUTH2 flow setup using the > external Python script (you'll need an "app" with a client ID / secret > that you may need an org administrator to create or approve), my guess > is Okta SSO will also work, since it will just be inline with whatever > web-based signin process you need. In the past, I did use that python script for mutt with oauth, but that was years ago at a job where oauth was used for internal single sign-on generally. Haven't tried integrating that approach with okta. Do you know of any guides online that outline how to do that? -- Cos
