diff options
| author | Eduardo Chappa <chappa@washington.edu> | 2020-07-09 00:16:36 -0600 |
|---|---|---|
| committer | Eduardo Chappa <chappa@washington.edu> | 2020-07-09 00:16:36 -0600 |
| commit | 0f89ad88df81df9d2ca7eafa276fecf8206fb598 (patch) | |
| tree | b8c24c61a7b9959241c5bfc0d95b7fe2f595c323 /pith | |
| parent | 560dd4993146181912c3bb98f6b26f7ed7f4de5d (diff) | |
| download | alpine-0f89ad88df81df9d2ca7eafa276fecf8206fb598.tar.xz | |
* Add choice of Authorization flow to Alpine. Alpine supports two ways to get
authorization to read email. One is called "Authorize" and the other "Device".
Some servers support both, some only one. For servers that support both, Alpine
will ask if it does not know which method to choose. Inspired by a conversation
with Pieter Jacques.
Diffstat (limited to 'pith')
| -rw-r--r-- | pith/pine.hlp | 36 |
1 files changed, 35 insertions, 1 deletions
diff --git a/pith/pine.hlp b/pith/pine.hlp index b751666b..903873c2 100644 --- a/pith/pine.hlp +++ b/pith/pine.hlp @@ -140,7 +140,7 @@ with help text for the config screen and the composer that didn't have any reasonable place to be called from. Dummy change to get revision in pine.hlp ============= h_revision ================= -Alpine Commit 486 2020-07-07 14:25:41 +Alpine Commit 488 2020-07-09 00:16:30 ============= h_news ================= <HTML> <HEAD> @@ -16233,6 +16233,40 @@ organization only. <End of help on this topic> </BODY> </HTML> +======= h_config_xoauth2_flow ======= +<HTML> +<HEAD> +<TITLE>Flow Explained</TITLE> +</HEAD> +<BODY> +<H1>Flow Explained</H1> + +The first time you connect to a service to authorize Alpine access to your +email, you will have to do a certain number of steps, which typically involve +to login to your account using a browser, and agreeing to give Alpine certain +rights to access your account. + +<P> +How this process is going to be done depends on the service. Some services +allow you to give access to Alpine and later generate a code that you +input into Alpine, while others give you a code you have to use before you +approve access to Alpine to access your email. + +<P> An example of a service that gives you a code after you authorize +Alpine is Gmail, and this process is called internally as "Authorize". +An example of a service that gives you a code before you authorize Alpine +is Outlook, and this process is called "Device". However, some services, +like Outlook, offer both services, and you can choose which flow you would like +to use. You +can choose between the "Authorize&qupt; and "Device" in these servers. +If you forget to configure +this, Alpine will ask you in these situations which method to use before it starts +to setup the process to get your authrization. + +<P> +<End of help on this topic> +</BODY> +</HTML> ======= h_config_xoauth2_username ======= <HTML> <HEAD> |