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

Revoking authorization uses the access token instead of the refresh token #59

Open
MathiasTortelboom opened this issue Apr 23, 2021 · 0 comments · May be fixed by #81
Open

Revoking authorization uses the access token instead of the refresh token #59

MathiasTortelboom opened this issue Apr 23, 2021 · 0 comments · May be fixed by #81

Comments

@MathiasTortelboom
Copy link

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:

def revoke_authorization(self):

'token': self.auth.access_token,

This gives issues when the access token has expired.
Is there a specific reason the access token is used here?

@yuekui yuekui linked a pull request May 26, 2022 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant