libre.sh/keycloak-scim
2
0
Fork 0
Code Issues 14 Pull requests Releases Packages Activity Actions 6

Keycloak not starting with legacy version (wildfly) #14

New issue
Closed
opened 2022-06-14 08:22:25 +00:00 by Hofer · 6 comments
Hofer commented 2022-06-14 08:22:25 +00:00 (Migrated from lab.libreho.st)
Copy link

With the newest commit I can't get kc running in local docker it just fails and on k8s the same thing:

My Dockerfile is the following:

FROM quay.io/keycloak/keycloak:16.1.1

RUN curl "https://lab.libreho.st/libre.sh/scim/keycloak-scim/-/jobs/artifacts/main/raw/build/libs/keycloak-scim-1.0-SNAPSHOT.jar?job=package" -Lo /opt/jboss/keycloak/standalone/deployments/keycloak-scim-1.0-SNAPSHOT.jar
COPY dependencies/resilience4j-core-1.7.1.jar /opt/jboss/keycloak/standalone/deployments/resilience4j-core-1.7.1.jar
COPY dependencies/resilience4j-retry-1.7.1.jar /opt/jboss/keycloak/standalone/deployments/resilience4j-retry-1.7.1.jar
COPY dependencies/scim2-sdk-client-2.3.7.jar /opt/jboss/keycloak/standalone/deployments/scim2-sdk-client-2.3.7.jar
COPY dependencies/scim2-sdk-common-2.3.7.jar /opt/jboss/keycloak/standalone/deployments/scim2-sdk-common-2.3.7.jar
COPY dependencies/slf4j-api-1.7.30.jar /opt/jboss/keycloak/standalone/deployments/slf4j-api-1.7.30.jar
COPY dependencies/vavr-0.10.2.jar /opt/jboss/keycloak/standalone/deployments/vavr-0.10.2.jar
COPY dependencies/vavr-match-0.10.2.jar /opt/jboss/keycloak/standalone/deployments/vavr-match-0.10.2.jar

Server fails after the following log

FATAL [org.keycloak.services] (ServerService Thread Pool -- 67) Error during startup: java.util.ServiceConfigurationError: org.keycloak.storage.UserStorageProvider
Factory: Provider sh.libre.scim.storage.ScimStorageProviderFactory could not be instantiated
With the newest commit I can't get kc running in local docker it just fails and on k8s the same thing: My Dockerfile is the following: ``` FROM quay.io/keycloak/keycloak:16.1.1 RUN curl "https://lab.libreho.st/libre.sh/scim/keycloak-scim/-/jobs/artifacts/main/raw/build/libs/keycloak-scim-1.0-SNAPSHOT.jar?job=package" -Lo /opt/jboss/keycloak/standalone/deployments/keycloak-scim-1.0-SNAPSHOT.jar COPY dependencies/resilience4j-core-1.7.1.jar /opt/jboss/keycloak/standalone/deployments/resilience4j-core-1.7.1.jar COPY dependencies/resilience4j-retry-1.7.1.jar /opt/jboss/keycloak/standalone/deployments/resilience4j-retry-1.7.1.jar COPY dependencies/scim2-sdk-client-2.3.7.jar /opt/jboss/keycloak/standalone/deployments/scim2-sdk-client-2.3.7.jar COPY dependencies/scim2-sdk-common-2.3.7.jar /opt/jboss/keycloak/standalone/deployments/scim2-sdk-common-2.3.7.jar COPY dependencies/slf4j-api-1.7.30.jar /opt/jboss/keycloak/standalone/deployments/slf4j-api-1.7.30.jar COPY dependencies/vavr-0.10.2.jar /opt/jboss/keycloak/standalone/deployments/vavr-0.10.2.jar COPY dependencies/vavr-match-0.10.2.jar /opt/jboss/keycloak/standalone/deployments/vavr-match-0.10.2.jar ``` Server fails after the following log ``` FATAL [org.keycloak.services] (ServerService Thread Pool -- 67) Error during startup: java.util.ServiceConfigurationError: org.keycloak.storage.UserStorageProvider Factory: Provider sh.libre.scim.storage.ScimStorageProviderFactory could not be instantiated ```
Hofer (Migrated from lab.libreho.st) closed this issue 2022-06-14 08:22:32 +00:00
Hofer commented 2022-06-14 08:22:36 +00:00 (Migrated from lab.libreho.st)
Copy link

changed title from Keycloak not starting with version 16.1.1{--legacy-} to Keycloak not starting with version 16.1.1

changed title from **Keycloak not starting with version 16.1.1{--legacy-}** to **Keycloak not starting with version 16.1.1**
Hofer (Migrated from lab.libreho.st) reopened this issue 2022-06-14 08:23:35 +00:00
Hofer commented 2022-06-14 09:21:45 +00:00 (Migrated from lab.libreho.st)
Copy link

Tried it on 18.0.0 legacy - same issue. Full log kc.log

Tried it on 18.0.0 legacy - same issue. Full log [kc.log](/uploads/63cb0b8634e9847871e583a3292bf947/kc.log)
Hofer commented 2022-06-14 09:23:15 +00:00 (Migrated from lab.libreho.st)
Copy link

changed title from Keycloak not starting with version {-16.1.1-} to Keycloak not starting with {+legacy +}version {+(wildfly)+}

changed title from **Keycloak not starting with version {-16.1.1-}** to **Keycloak not starting with {+legacy +}version {+(wildfly)+}**
hugo.renard commented 2022-06-14 10:49:40 +00:00 (Migrated from lab.libreho.st)
Copy link

It seems dependencies are not loaded or not in the right order. (Caused by: java.lang.NoClassDefFoundError: com/unboundid/scim2/client/ScimService).
I saw other projects loading dependencies like this. It should work, but surly I missed something.

It seems dependencies are not loaded or not in the right order. (`Caused by: java.lang.NoClassDefFoundError: com/unboundid/scim2/client/ScimService)`. I saw other projects loading dependencies like this. It should work, but surly I missed something.
hugo.renard commented 2022-06-14 17:50:03 +00:00 (Migrated from lab.libreho.st)
Copy link

Okay, It may br because the jboss-deployment-structure.xml is incomplete. I'll try when I can, but if you have some time, It's worth trying.

Okay, It may br because the `jboss-deployment-structure.xml` is incomplete. I'll try when I can, but if you have some time, It's worth trying.
Hofer commented 2022-06-15 06:53:37 +00:00 (Migrated from lab.libreho.st)
Copy link

Ok thanks.

Ok thanks.
Hofer (Migrated from lab.libreho.st) closed this issue 2022-07-25 10:58:44 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
scim-support-13484
feat/ci
develop
0.0.7
0.0.6
0.0.5
0.0.4
0.0.3
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: libre.sh/keycloak-scim#14
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?