Skip to content

Conversation

@tcnichol
Copy link
Contributor

With keycloak v20, openid is not included as a default scope, which caused the error reported by the upgrade.

On the issue there is a video that shows how I configured keycloak through the admi console to work.

I did an export of the realm.json and I believe that all the keycloak json files are now working and correct. The dev one definitely works.

Marking this draft as I need to check whether the other jsons work.

@tcnichol tcnichol linked an issue Jan 23, 2024 that may be closed by this pull request
@tcnichol tcnichol requested a review from ddey2 January 23, 2024 18:02
@tcnichol
Copy link
Contributor Author

I have tested this with both docker-dev and docker compose and it works.

I was not sure what to do to test other keycloak json files that I modified, but I will make this a pull request and not draft.

@tcnichol tcnichol marked this pull request as ready for review January 23, 2024 22:32
Copy link
Member

@longshuicy longshuicy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you also update the k8s deployment realm at deployments/kubernetes/charts/clowder2/files/realm.json if possible?

@tcnichol
Copy link
Contributor Author

Could you also update the k8s deployment realm at deployments/kubernetes/charts/clowder2/files/realm.json if possible?

Added.

@longshuicy longshuicy merged commit fd7ee00 into main Feb 1, 2024
@longshuicy longshuicy deleted the 891-upgrade-keycloak branch February 1, 2024 19:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

upgrade keycloak

3 participants