-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/keycloak-config-cli] Importing Realm With Identity Provider Error #29851
Comments
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here. Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance. |
This appears to be due to Keycloak Config CLI not currently supporting Keycloak 26 (adorsys/keycloak-config-cli#1160)
I am experiencing this in testing upgrading $ k get job keycloak-keycloak-config-cli -o yaml | grep image
image: docker.io/bitnami/keycloak-config-cli:6.1.6-debian-12-r4 $ k get job keycloak-keycloak-config-cli -o jsonpath='{.metadata.labels}' | jq
{
"app.kubernetes.io/component": "keycloak-config-cli",
"app.kubernetes.io/instance": "keycloak",
"app.kubernetes.io/managed-by": "Helm",
"app.kubernetes.io/name": "keycloak",
"app.kubernetes.io/version": "26.0.0",
"helm.sh/chart": "keycloak-24.0.0",
"tags.datadoghq.com/env": "local",
"tags.datadoghq.com/service": "keycloak",
"tags.datadoghq.com/version": "26.0.0"
} |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
I don't think this issue is stale, but I think it should be reworded to something along the lines of "Keycloak Config CLI doesn't currently support Keycloak 26 so But maybe a little more concise than that ^ |
I'm finding the same issue now, but with 26.0.5 it means the job shows as Failed. Ideally this should be documented somewhere
|
There's a PR open for updating Keycloak Config CLI to Keycloak 26. |
adorsys/keycloak-config-cli#1162 has been merged, now for the Bitnami container to be built 🙌 |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
I don't think this is stale. |
Keycloak Config CLI |
The docker image isn't ready yet. See adorsys/keycloak-config-cli#1220 (comment). |
Looks like Bitnami has built their version of the Keycloak Config CLI - bitnami/containers#75511 Now we just need to wait for the Helm chart to be updated 🥳 |
I have confirmed ability to create realms via the keycloak:
enabled: true
auth:
adminUser: "admin"
adminPassword: "admin"
postgresql:
enabled: true
ingress:
enabled: true
ingressClassName: "nginx"
pathType: ImplementationSpecific
hostname: keycloak.local
path: "/"
annotations:
kubernetes.io/ingress.class: "nginx"
nginx.ingress.kubernetes.io/rewrite-target: /
keycloakConfigCli:
enabled: true
image:
tag: 6.2.0-debian-12-r0
configuration:
test.json: |
{
"realm": "test",
"enabled": true,
"clients": [
{
"clientId": "test-client",
"secret": "test-client-secret",
"protocol": "openid-connect",
"redirectUris": ["http://test.local/*"],
"publicClient": false,
"directAccessGrantsEnabled": true
}
]
} |
Name and Version
bitnami/keycloak-config-cli:6.1.6-debian-12-r4
What architecture are you using?
amd64
What steps will reproduce the bug?
What is the expected behavior?
When exporting a realm as json manually, we can see that
hideOnLogin
is included as a property ofidentityProviders
.keycloak-config-cli should identify
hideOnLogin
as a valid field foridentityProviders
.What do you see instead?
The error above suggests that keycloak-config-cli does not currently have the correct definition for the property in question.
Additional information
Checking the upstream source, note that a similar definition exists, but it is nested within the
config
property, and possesses the namehideOnLoginPage
.The text was updated successfully, but these errors were encountered: