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

chore: remove caching in the user info endpoint in the backend #108

Open
bonyfusbouvet opened this issue Aug 14, 2023 · 3 comments
Open
Assignees
Labels

Comments

@bonyfusbouvet
Copy link
Contributor

Remove caching in the the user info endpoint in the backend.

@vehecap
Copy link

vehecap commented Nov 26, 2024

Investigate why this should be removed. Connect with Bon if it is not obvious.

@mikkel1ea
Copy link
Contributor

If I remember correctly it was due to issues where the user info would be cached, so even though a user had gotten new accesses they wouldn't be able to access the correct plants, where you had to reset manually to repopulate the cache.

A simple way of testing this would be to simply add a new location to one of the members in your team, and see if this they get access to it when everything is synced up in backend.

@ashukequinor
Copy link
Contributor

deployed on dev

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

No branches or pull requests

4 participants