powerup client.isAuthorized() is still returning true after powerup access has been revoked

[Pete Williams]

I testing authorisation capabilities for my powerup but have run into difficulties. Having got my powerup authorised for my test user I now want to change the authorisation scope. To do this, I've revoked access to my powerup from my test users settings panel, changed the scope for authorisation and rerun the authorisation setup as suggested in the documentation. The trouble is the powerup api gives every indication that the powerup is already authorised, and as a consequence any attempt to reauthorise does nothing.

Does anyone have advice as to how to solve this problem?

[bentley]

I'd also recommend checking out the Trello Developers Community: https://community.developer.atlassian.com/c/trello. This is a great place to ask developer-related questions for Trello.

[bentley]

@Pete Williams Which method of authorization are you using?

It sounds like you might be using the REST API Client as documented here: https://developers.trello.com/reference#rest-api-client. If so,  you'll want to use `client.clearToken()` to remove the token that you have stored. Documentation for `client.clearToken()` here:  https://developers.trello.com/reference#client-cleartoken.

One thing that the REST API Client doesn't do is regularly ensure that the token that you have stored is still a valid, working token. As you've run into, it is possible for it to hold onto an invalid token for you.