On Sun, Mar 12, 2023 at 03:10:54PM +0200, Victor Ustugov via Exim-users wrote:
> https://packages.debian.org/source/sid/exim4 to it. I mean 75_*.patch
>
> Script get_oauth2_access_token-v.corvax.test@gmail.com.sh is based on
> https://github.com/pcw11211/exim4-oauth2/blob/main/get_bearer_tocken.sh
>
> This is just a prototype. I'm going to cache responses to requests to
> get an access_token, taking into account the expires_in value, in order
> to reduce the number of HTTP requests.
For what it is worth, I am doing this already in my Oauth script for use
with MS servers. I use gawk to do that part. It would be on Gitlab
already if it were not for real life in the way of a failing car battery
getting in the way.
> Client id, client secret and refresh token will be stored in the
> database, so there will be no need to create a script to get an access
> token for each user.
But I am not doing that, so far at least.
For information, I will attach the README.md for my script as it stands today.
ael
> https://packages.debian.org/source/sid/exim4 to it. I mean 75_*.patch
>
> Script get_oauth2_access_token-v.corvax.test@gmail.com.sh is based on
> https://github.com/pcw11211/exim4-oauth2/blob/main/get_bearer_tocken.sh
>
> This is just a prototype. I'm going to cache responses to requests to
> get an access_token, taking into account the expires_in value, in order
> to reduce the number of HTTP requests.
For what it is worth, I am doing this already in my Oauth script for use
with MS servers. I use gawk to do that part. It would be on Gitlab
already if it were not for real life in the way of a failing car battery
getting in the way.
> Client id, client secret and refresh token will be stored in the
> database, so there will be no need to create a script to get an access
> token for each user.
But I am not doing that, so far at least.
For information, I will attach the README.md for my script as it stands today.
ael