Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Acquiring new token fails if a token is not older than 30 days #19

Open
iamrgroot opened this issue Apr 6, 2022 · 2 comments
Open

Acquiring new token fails if a token is not older than 30 days #19

iamrgroot opened this issue Apr 6, 2022 · 2 comments

Comments

@iamrgroot
Copy link

Exact has a fairly new policy that if a token is not used for 30 days you should use a new authorization request in stead of a refresh token request:

https://support.exactonline.com/community/s/knowledge-base#All-All-DNO-Content-oauth-eol-oauth-devstep4
image

Could this be incorporated in this package? Right now, if you have a refresh token that is older than 30 days in your JSON config (stored on disk), the connection crashes on an error 400 because the refresh token is too old.

@JordivdB
Copy link

Did you find the solution to this? Having the same problem.

@iamrgroot
Copy link
Author

Did you find the solution to this? Having the same problem.

Sadly nope, we had to fix it manually: check if the token date is too old, remove the json with the token and start the auth process again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants