Closed
Description
Description
For resources, Keycloak maintains a resource identified in the table migration_model. If that changes with a newly deployed version, all resource URLs change.
Due to that, Keycloak will today respond to all old URLs with a 404. Responding with a redirect to current version of the resource might be a better choice.
Discussion
No response
Motivation
- For the login theme, the resources referenced there change usually not much in patch releases (for example the CSS). Even if it is wrong, it is worth a try to retrieve it.
- With the admin and account UI, the JS resources are bundled with a shortened hash in the filename. If the file exists with the same suffix, its contents will be identical. It can then be served (if it exists locally) after ignoring the resource version.
- As outlined in the parent epic, zero downtime patch releases will recommend sticky sessions to avoid this situation from happening, and clients bouncing between nodes too much.
- In a mixed cluster, some redirects might happen between nodes. After too many redirects the browser will eventually stop. This is then again a best effort approach, and shouldn't happen often given sticky sessions are recommended.
Details
No response