Fixed internal server error when enabling keycloak on existing installation #62
+23
−12
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.
Fixes #61
When you rerun engine-setup to activate Keycloak, it can't find the OVESETUP_CONFIG/adminPassword value in the environmental variables. This becomes a problem when you're setting up Keycloak alone because it needs that password to correctly finish the setup. Since we can't fetch the password in plain text from anywhere, we ask the user to enter the engine password so the setup can complete successfully.
Note: This is not an issue when setting up a fresh installation with engine-setup (and immediately activating keycloak), because the password is stored in the environmental variables.