BUG: JFConnect is enabled in artifactory OSS version

[dawidstrozak]

Problem

It looks like JFConnect is enabled in 107.133.12 OSS version.
As I understand this microservice shouldn't be working/required within the OSS version as it is responsible for license management etc.

It looks like this microservice is not even present within the OSS yet artifactory frontend still seems to try and reach it.
After upgrading from 107.117.19 to 107.133.12 I saw following issues:

• Frontend would just load forever in the browser
• Following errors logs were thrown by the frontend microservice:

kubectl logs -n artifactory artifactory-oss-0 -c frontend -f
2026-03-13T09:52:22.090Z [jffe ] [ERROR] [] [frontend-service.log] [main                ] - init entitlements failed||  uncaughtException detected
2026-03-13T09:52:22.090Z [jffe ] [ERROR] [] [frontend-service.log] [main                ] - Error: init entitlements failed
    at EntitlementsStore.init (/opt/jfrog/artifactory/app/frontend/bin/server/dist/node_modules/@jfrog/jfconnect-nodejs-client/dist/EntitlementsStore.js:16:23)
    at JFConnectClient.init (/opt/jfrog/artifactory/app/frontend/bin/server/dist/node_modules/@jfrog/jfconnect-nodejs-client/dist/JFConnectClient.js:31:9)
    at Function.initClient (/opt/jfrog/artifactory/app/frontend/bin/server/dist/webpack:/src/Services/JFConnectService.ts:68:3)
    at Function.getClient (/opt/jfrog/artifactory/app/frontend/bin/server/dist/webpack:/src/Services/JFConnectService.ts:55:13)
    at Function.getEntitlements (/opt/jfrog/artifactory/app/frontend/bin/server/dist/webpack:/src/Services/JFConnectService.ts:181:18)
    at getEntitlements (/opt/jfrog/artifactory/app/frontend/bin/server/dist/webpack:/src/Controllers/JFConnectController.ts:20:28)
2026-03-13T09:52:29.302Z backoffice-metrics-service [debug] - Log worker started collecting metrics for providers ...
2026-03-13T09:53:26.086Z [jffe ] [WARN ] [00-01668a5eacd5b731db7f755d903513a1-8b0f52848b086f4a-01] [frontend-service.log] [main                ] - count fetch entitlements: 12 UNIMPLEMENTED: Received HTTP status code 404 Attempt: 5
2026-03-13T09:53:31.097Z [jffe ] [WARN ] [00-01668a5eacd5b731db7f755d903513a1-8b0f52848b086f4a-01] [frontend-service.log] [main                ] - count fetch entitlements: 12 UNIMPLEMENTED: Received HTTP status code 404 Attempt: 10
2026-03-13T09:53:36.111Z [jffe ] [WARN ] [00-01668a5eacd5b731db7f755d903513a1-8b0f52848b086f4a-01] [frontend-service.log] [main                ] - count fetch entitlements: 12 UNIMPLEMENTED: Received HTTP status code 404 Attempt: 15
2026-03-13T09:53:41.125Z [jffe ] [WARN ] [00-01668a5eacd5b731db7f755d903513a1-8b0f52848b086f4a-01] [frontend-service.log] [main                ] - count fetch entitlements: 12 UNIMPLEMENTED: Received HTTP status code 404 Attempt: 20
2026-03-13T09:53:46.138Z [jffe ] [WARN ] [00-01668a5eacd5b731db7f755d903513a1-8b0f52848b086f4a-01] [frontend-service.log] [main                ] - count fetch entitlements: 12 UNIMPLEMENTED: Received HTTP status code 404 Attempt: 25
2026-03-13T09:53:51.153Z [jffe ] [WARN ] [00-01668a5eacd5b731db7f755d903513a1-8b0f52848b086f4a-01] [frontend-service.log] [main                ] - count fetch entitlements: 12 UNIMPLEMENTED: Received HTTP status code 404 Attempt: 30
2026-03-13T09:53:56.168Z [jffe ] [WARN ] [00-01668a5eacd5b731db7f755d903513a1-8b0f52848b086f4a-01] [frontend-service.log] [main                ] - count fetch entitlements: 12 UNIMPLEMENTED: Received HTTP status code 404 Attempt: 35

Workaround
I managed to resolve this issue by disabling JFConnect within system.yaml config like so:

  values:
    artifactory:
      artifactory:
        systemYaml: |
          jfconnect:
            enabled: false

With this change Frontend loads normally and the previous errors are gone.
All I can see is an entitlement warning like so:

2026-03-13T10:41:54.682Z [jffe ] [WARN ] [00-d38792258e7a6a436fea5272583ed4cd-42c041b168f5ddd0-01] [frontend-service.log] [main                ] - JFConnect is disabled, Entitlements were accessed while jfconnect is disabled.

This is the exact same log I can also see on the 107.117.19 so this tells me that within the older version of this chart JFConnect is disabled by default resulting in working configuration. While in the latest version configuration is broken by default and needs jfconnect to be explicitly disabled.

Suggested fix
Fix the issue by setting jfconnect to disabled by default in OSS like it was in older versions.
Alternatively update documentation and make it very clear that this is required to have a working artifactory-oss.

[chukka]

Thanks for reporting , I'll check and come back shortly

[chukka]

@dawidstrozak I tried it with the latest 7.133.12 version on a fresh install, and it works as expected. Could you please share the reproducible steps for your scenario?

[dawidstrozak]

We had artifactory-oss running on version 107.117.19 and I simply upgraded the chart version to 107.133.12 (we use Flux CD).

Here is our chart:

apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: artifactory-oss
  namespace: artifactory
spec:
  timeout: 20m
  releaseName: artifactory-oss
  chart:
    spec:
      chart: artifactory-oss
      version: 107.133.12
      sourceRef:
        kind: HelmRepository
        name: artifactory
        namespace: artifactory
  interval: 1m
  values:
    artifactory:
      artifactory:
        admin:
          secret: <secret>
          dataKey: <creds>
        consoleLog: true
        joinKeySecretName: <key>
        masterKeySecretName: <master-key>
        persistence:
          storageClassName: managed
          size: 128Gi
        database:
          allowNonPostgresql: true
        systemYaml: |
          shared:
            database:
              allowNonPostgresql: true
          jfconnect: # <-- Adding this fixed the issue
            enabled: false
        configMapName: <config-map>
      ingress:
        annotations:
          traefik.ingress.kubernetes.io/router.tls: "true"
        className: traefik
        enabled: true
      nginx:
        enabled: false
      postgresql:
        enabled: false
    postgresql:
      enabled: false

[viko97-a12]

I'm having the same issue using the latest OSS version, i tried installing it using docker-compose in a VM, also systemd, and every time the error was the same

2026-03-27T13:52:12.351Z [jfac ] [INFO ] [bfd79d037a8223c4] [TokenExpiryWorkerNotifyTask:80] [task-pool-6-thread-7] - Running notify on token expiry task 2026-03-27T13:52:16.998Z [jffe ] [WARN ] [00-39d18a6fe03dede29eb3f9a943a1f803-e5f951a572dfea92-01] [frontend-service.log] [main ] - count fetch entitlements: 12 UNIMPLEMENTED: Received HTTP status code 404 Attempt: 10 2026-03-27T13:52:22.022Z [jffe ] [WARN ] [00-39d18a6fe03dede29eb3f9a943a1f803-e5f951a572dfea92-01] [frontend-service.log] [main ] - count fetch entitlements: 12 UNIMPLEMENTED: Received HTTP status code 404 Attempt: 15 2026-03-27T13:52:27.051Z [jffe ] [WARN ] [00-39d18a6fe03dede29eb3f9a943a1f803-e5f951a572dfea92-01] [frontend-service.log] [main ] - count fetch entitlements: 12 UNIMPLEMENTED: Received HTTP status code 404 Attempt: 20 2026-03-27T13:52:32.074Z [jffe ] [WARN ] [00-39d18a6fe03dede29eb3f9a943a1f803-e5f951a572dfea92-01] [frontend-service.log] [main ] - count fetch entitlements: 12 UNIMPLEMENTED: Received HTTP status code 404 Attempt: 25 2026-03-27T13:52:37.100Z [jffe ] [WARN ] [00-39d18a6fe03dede29eb3f9a943a1f803-e5f951a572dfea92-01] [frontend-service.log] [main ] - count fetch entitlements: 12 UNIMPLEMENTED: Received HTTP status code 404 Attempt: 30 2026-03-27T13:52:42.124Z [jffe ] [WARN ] [00-39d18a6fe03dede29eb3f9a943a1f803-e5f951a572dfea92-01] [frontend-service.log] [main ] - count fetch entitlements: 12 UNIMPLEMENTED: Received HTTP status code 404 Attempt: 35

Versions that i tried installing it, I'm doing a fresh install - 7.133.15, 7.133.12, 7.104.15 and still the same....

We have another production PRO version with version 7.104.15, there we don't have issues, but it was installed/upgraded last year and it's working fine, but now I have another use case and i need to use -oss package.