Revoke Token API not Working Properly.
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.
-
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.
-
Hi Appu, just an update...my dev team confirmed today that this is not working as expected and they've opened up a card in their backlog to get this fixed. I don't have an ETA at the moment, so I would recommend using the id method for now and as soon as they have a fix deployed, I'll confirm it and let you know. Thanks again for reporting this issue!
-
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.
-
I would also like to escalate this issue, my team and I have run into the same problem: when can we expect a fix?
-
Hi all! The dev team has added this to their backlog, but there is no current ETA for a solution. When we have an ETA or a fix in place, I'll drop an update here.
-
Is there any updates on this Greg Katechis?
-
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. -
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.
-
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
-
Any updates on this Greg Katechis?
댓글을 남기려면 로그인하세요.
10 댓글