Fix: Keycloak Refresh Tokens before Expiry #190
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Currently, users are forced to refresh the Hephaestus-Website (every 30 minutes) when the access token expires and subsequent requests include invalid authentication/JWT token.
Description
This PR fixes the token expiry issue by adding a refresh interval checking for expiry every 60 seconds. Keycloak then refreshes the token itself (triggers a new request to the Keycloak-server).
The PR implements ideas from this best practices guide: https://github.com/akoserwal/keycloak-integrations/blob/main/angular-keycloak/src/main.ts
Additional security suggestions from this Medium article could indepently used for higher security.
Testing Instructions
application-server
andwebapp
Screenshots (if applicable)
Checklist
General