Stephen Isard wrote in <21561-1681760808-258...@sneakemail.com>: |On Mon, 17 Apr 2023, Steffen Nurpmeso steffen-at-sdaoden.eu |s-nail| wrote: |> But client_secret is definetely not freely inventable by users, |> but if available is linked to the application. |> Alpine .. seems to have added an Outlook client_secret on |> 2020-07-09 with 0f89ad88df81df9d2ca7eafa276fecf8206fb598, and did |> not have one before. Maybe with paying or something you can |> choose a longer validity than 30 months? It passed the 30 months |> by now, that much is plain. | |The interval between alpine reauthorizations has definitely been less |than 30 months. More like 6, although I haven't tried to keep track. |It's infrequent enough, and easy enough to do, that it isn't a problem. | |> you are the only person i know who sits |> "in some special department" that causes additional access checks |> to kick in. And lucky that your own configuration works. | |Yes, I'm ok and not asking you to do anything for my sake at this point. |I only replied to your message "for information".
Thank you Stephen. Please wait ... Ok, so i tried with Microsoft, and why oauth-helper.py looses the refresh_token, but not the access_token. It turns out that Microsoft change their policy, and, even though totally out-of-standard RFC 6749, they now require the "scope" to be passed around always. I fixed that, and for me the Microsoft stuff works again completely. (They however strip "offline_access" from it, and we faithfully take what they give us iirc.) I am only a lonely user and what do i know of your setup. On the other hand bandwidth is now totally borked, and with 64kbit none of the giants work today, so OAuth login is almost impossible. I hope it works. Ciao. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
