fix(deployment): add old keycloak flags #3735
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
corneliusroemer
approved these changes
Feb 24, 2025
|
Note 2 tests fail and I haven't checked why. They should be checked before merge |
|
Made issue #3736 to upgrade keycloak, might be good to reference this issue in the code as well :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
resolves #3618 for now
preview URL: https://authentication-kcflags.loculus.org/admin/master/console (admin/admin)
Summary
We upgraded the keycloak environment variable flags without upgrading keycloak itself, meaning an admin account with a known admin password is not created. This is an unfortunate breakage on main for anyone wanting to try out Loculus for their own use, and prevents us logging in ourselves (except on pathoplexus).
Here I add the old flags back as duplicates to mitigate.