You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, although during the development I realized that the refresh_token is the only relevant secret regarding the XOAuth2 authentication, I just verified that I could run ./integration-test.sh xoauth2 with the token file that I had since last week. So I think that you can enable integration tests by:
Login once with the testing account to obtain refresh_token and access_token
Store these secrets as github secrets.
Generate the .env with using the stored secrets to initialize XOAUTH2_INITIAL_ACCESS_TOKEN and XOAUTH2_INITIAL_REFRESH_TOKEN.
Although in a proper installation these variables are only used once to initialize the internal token database, seems that the XOAuth2 library can refresh the access_token without problem.
The text was updated successfully, but these errors were encountered:
Yesterday I setup (with the same secrets) a instance of the latest container in a different machine and it worked. The only thing it is that I have enabled 2FA for that account.
Hi, although during the development I realized that the
refresh_token
is the only relevant secret regarding the XOAuth2 authentication, I just verified that I could run./integration-test.sh xoauth2
with the token file that I had since last week. So I think that you can enable integration tests by:refresh_token
andaccess_token
.env
with using the stored secrets to initializeXOAUTH2_INITIAL_ACCESS_TOKEN
andXOAUTH2_INITIAL_REFRESH_TOKEN
.Although in a proper installation these variables are only used once to initialize the internal token database, seems that the XOAuth2 library can refresh the access_token without problem.
The text was updated successfully, but these errors were encountered: