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

If an access token is revoked, Aggregator doesn't update "authorized" status #114

Open
mstenta opened this issue Apr 1, 2022 · 1 comment

Comments

@mstenta
Copy link
Member

mstenta commented Apr 1, 2022

(Showed this to @paul121 on screenshare... can add more details later...)

@mstenta
Copy link
Member Author

mstenta commented Apr 1, 2022

Quick notes and steps to reproduce:

It seems that when an access token is revoked on the farmOS server, the Aggregator doesn't properly detect that it is no longer authorized, so the status in the Aggregator > Manage Farms UI still shows green "Authorized". Sending API requests to the farmOS instance fail with 401 Client Error: Unauthorized for url: [endpoint].

Clicking the refresh button in the Aggregator UI does not fix this, nor does it give any indication that anything is wrong.

This may also be the cause of #115... which was encountered in the same testing.

To reproduce, revoke the access token in a farmOS instance. An easy way to do this is to change the authorized user's roles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant