Non-interactive / automated authentication #354
-
|
Hi, I guess it's just me but I can't seem to wrap my head around non-interactive authentication. I got it all running with my O365 testing account. Working out great. Had to use local-server-auth to retrieve the token(s). But now i would like to use it for some automated SMTP to O365 "relaying" service - essentially basic auth mails coming in and getting relayed via some Oauth O365 mailbox. If I'm not mistaken my refresh token will expire some time down the road - breaking the mail flow for that time? Is there some form of supported authentication flow that can be used for fuly automated / non-interactive (re-)authentication? Thank you very much! What agreat project :) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The proxy automatically renews access tokens (using the refresh token), but once the refresh token itself expires there is no alternative: you must interactively authenticate. The Auth-Email service makes this easier by putting the authentication request into a browser dashboard rather than in the terminal. Alternatively, you can use a fully non-interactive OAuth flow (such as CCG, ROPCG, service account). |
Beta Was this translation helpful? Give feedback.
The proxy automatically renews access tokens (using the refresh token), but once the refresh token itself expires there is no alternative: you must interactively authenticate. The Auth-Email service makes this easier by putting the authentication request into a browser dashboard rather than in the terminal. Alternatively, you can use a fully non-interactive OAuth flow (such as CCG, ROPCG, service account).