Recent searches
No recent searches
Revoke Token API not Working Properly.
Posted Mar 29, 2023
When revoking an Access Token using the ID of the Token, it gets revoked with no problem.
DELETE /api/v2/oauth/tokens/{oauth_token_id}
But when revoking it with current.json endpoint, the response we get is 204 but the token is not revoked. We have full write and read access with that token. But I don't know why it not get revoked.
DELETE /api/v2/oauth/tokens/current.json
Looking for your reply. Thanks.
1
18
18 comments
Greg Katechis
Hi Appu! Thanks for reporting this...I was just able to reproduce the issue. I've reached out to our team that handles this and I'll drop you a line when I hear back from them.
1
AppuSamy
Hi Greg Katechis,
Please resolve this issue as soon as possible. Because for implementation in our code I need to get the scope : read for every authorization, so that I can get the Token ID by calling OAuth Token API and revoke the Token. If current.json is working properly its a big relief and we can get only the specific scopes necessary for making requests.
Looking for your Reply.
Thanks.
Appu Samy.
0
Greg Katechis
1
Evan
I would also like to escalate this issue, my team and I have run into the same problem: when can we expect a fix?
0
Greg Katechis
0
AppuSamy
Is there any updates on this Greg Katechis?
0
AppuSamy
Hello Greg Katechis
I have tagged you like 2 1/2 weeks before, but you didn't even try to reply the message. We need this solution ASAP. By the way all of those who are using your APIs need this solution. Its not like they do it another way, please make this as priority and work on this to resolve the issue.
Let an issue persisting for this much time is not good. Its not like no one knows about this, we know and mentioned to you about this. I am expecting a positive response from you.
0
Greg Katechis
Hi Appu! As I mentioned in my comment on April 25, as soon as I have an update, I will drop a line in here. I do not have any control over that team's roadmap and they have quite a few high priority items already pending. I am actively watching the progress and when we have some more updates on this topic, I will drop a line in here.
0
Dinesh Local
on the same note, i revoked the token however when i signed in again on webpage of an app which takes me to the zendesk sign in page, but this time it did not bring up the page asking me to authorize to access zendesk.
This is a bug, after revoking token, it is not asking me to authorize
Dinesh
0
AppuSamy
Any updates on this Greg Katechis?
0
AppuSamy
Greg Katechis
Any updates on revoking token problem?
0
AppuSamy
Hello Greg
Is there any Updates on this?
Thanks,
AppuSamy
0
Greg Katechis
0
Dinesh Local
I revoked the latest token, and when i try to regenerate new token, the screen that should ask user to confirm the access, does not come up.
It is creating issue for us, if we want to add more scope as part of the new token, it is not alllowing that. Unless all the tokens for the users are deleted , is there any api call to delele all tokens for the user
0
Christopher Kennedy
When you try to get a new token, does your integration redirect the user to the authorization page with the new scope details? If so, are you receiving an error?
0
Dinesh Local
Yes, we redirect user t authorization page, however that page does not come up, unless all the previously generated tokens are not revoked, that puzzles me whey there are multiple tokens for the same user and same client id. So i had to retrive all the existing token and revoke them one afrer another, is this expected behavior for one user ot have multiple token.
Please let me know.
0
Dinesh Local
then I see the authorization page is coming up fine.
0
Dinesh Local
I am having issues with api call https://subdomain.zendesk.com/api/v2/oauth/tokens?client_id={client_id} only for one of client id which is only 4 digit long, it returns the empty response, however if i make call https://{subdomain}.zendesk.com/api/v2/oauth/tokens i see the response having client id, which i pass into first call, any reason why would it do, also since there multiple client_ids I see in the https://{subdomain}.zendesk.com/api/v2/oauth/tokens response. for others it returns correct response only the one with 4 digits is having issue
0