We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With the current approach of login users locally, there can be an scenario as following:
To solve this, the app could invalidate an apiKey once it gets an Auth error from the server, so the user has to login again and get a new apiKey.
The text was updated successfully, but these errors were encountered:
Thanks - yes that seems to be a good approach.
Sorry, something went wrong.
DigitalCampus#510: Added basic classes squeleton for the invalidation…
566bc16
… process
DigitalCampus#510: Implemented methods to validate and invalidate apiKey
1de05ac
DigitalCampus#510: Added the logic to logout the user once the apiKey…
5d906f2
… has been invalidated
DigitalCampus#510: Added apiKey logic in every place we make requests…
678ca83
… to the server
DigitalCampus#510: Login against server when the user's apiKey has be…
08a1663
…en invalidated
No branches or pull requests
With the current approach of login users locally, there can be an scenario as following:
To solve this, the app could invalidate an apiKey once it gets an Auth error from the server, so the user has to login again and get a new apiKey.
The text was updated successfully, but these errors were encountered: