We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Cronofy documentation (https://docs.cronofy.com/developers/api/authorization/revoke/) gives the following advice for revoking authorization:
It is recommended that you use the refresh_token as that cannot have expired and therefore be impossible to revoke
The revoke function uses the access token instead:
pycronofy/pycronofy/client.py
Line 531 in 59765fe
Line 539 in 59765fe
This gives issues when the access token has expired. Is there a specific reason the access token is used here?
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
The Cronofy documentation (https://docs.cronofy.com/developers/api/authorization/revoke/) gives the following advice for revoking authorization:
The revoke function uses the access token instead:
pycronofy/pycronofy/client.py
Line 531 in 59765fe
pycronofy/pycronofy/client.py
Line 539 in 59765fe
This gives issues when the access token has expired.
Is there a specific reason the access token is used here?
The text was updated successfully, but these errors were encountered: