deployed the latest kakfa-ui jar (version 0.7.2) using java -jar ，config complete , I couldn't see my cluster on the kafka-ui console page.

[silent-night-no-trace]

Issue submitter TODO list

• I've looked up my issue in FAQ
• I've searched for an already existing issues here
• I've tried running master-labeled docker image and the issue still persists there
• I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

I deployed the latest kakfa-ui jar (version 0.7.2) using java -jar. When I finished configuring it, I couldn't see my cluster on the kafka-ui console page.

Expected behavior

Use the kafka-ui console to manage existing kafka clusters

Your installation details

1. version 0.7.2
2. shell nohup java --add-opens java.rmi/javax.rmi.ssl=ALL-UNNAMED -jar ./kafka-ui-api-v0.7.2.jar --spring.profiles.active=local --spring.config.location=file:./application-local.yaml >./out.log 2>&1 &

logging:
  level:
    root: INFO
    com.provectus: DEBUG
    #org.springframework.http.codec.json.Jackson2JsonEncoder: DEBUG
    #org.springframework.http.codec.json.Jackson2JsonDecoder: DEBUG
    reactor.netty.http.server.AccessLog: INFO
    org.springframework.security: DEBUG

server:
 port: 18888

spring:
  jmx:
    enabled: false
  # ldap:
  #   urls: ldap://localhost:10389
  #   base: "cn={0},ou=people,dc=planetexpress,dc=com"
  #   admin-user: "cn=admin,dc=planetexpress,dc=com"
  #   admin-password: "GoodNewsEveryone"
  #   user-filter-search-base: "dc=planetexpress,dc=com"
  #   user-filter-search-filter: "(&(uid={0})(objectClass=inetOrgPerson))"
  #   group-filter-search-base: "ou=people,dc=planetexpress,dc=com"

kafka:
  clusters:
    - name: local
      bootstrapServers: xxx:9092
      # kafkaConnect:
      #   - name: first
      #     address: http://192.168.104.78:8083
      # metrics:
      #   port: 9997
      #   type: JMX

# dynamic.config.enabled: true

# oauth2:
#   ldap:
#     activeDirectory: false
#     aсtiveDirectory.domain: domain.com

auth:
  type: DISABLED
  #  type: OAUTH2
  #  type: LDAP
  # oauth2:
  #   client:
  #     cognito:
  #       clientId: # CLIENT ID
  #       clientSecret: # CLIENT SECRET
  #       scope: openid
  #       client-name: cognito
  #       provider: cognito
  #       redirect-uri: http://localhost:8080/login/oauth2/code/cognito
  #       authorization-grant-type: authorization_code
  #       issuer-uri: https://cognito-idp.eu-central-1.amazonaws.com/eu-central-1_M7cIUn1nj
  #       jwk-set-uri: https://cognito-idp.eu-central-1.amazonaws.com/eu-central-1_M7cIUn1nj/.well-known/jwks.json
  #       user-name-attribute: cognito:username
  #       custom-params:
  #         type: cognito
  #         logoutUrl: https://kafka-ui.auth.eu-central-1.amazoncognito.com/logout
  #     google:
  #       provider: google
  #       clientId: # CLIENT ID
  #       clientSecret: # CLIENT SECRET
  #       user-name-attribute: email
  #       custom-params:
  #         type: google
  #         allowedDomain: provectus.com
  #     github:
  #       provider: github
  #       clientId: # CLIENT ID
  #       clientSecret: # CLIENT SECRET
  #       scope:
  #         - read:org
  #       user-name-attribute: login
  #       custom-params:
  #         type: github

rbac:
  roles:
    - name: "memelords"
      clusters:
        - local
      subjects:
        - provider: oauth_google
          type: domain
          value: "provectus.com"
        - provider: oauth_google
          type: user
          value: "name@provectus.com"

        - provider: oauth_github
          type: organization
          value: "provectus"
        - provider: oauth_github
          type: user
          value: "memelord"

        - provider: oauth_cognito
          type: user
          value: "username"
        - provider: oauth_cognito
          type: group
          value: "memelords"

        - provider: ldap
          type: group
          value: "admin_staff"

        # NOT IMPLEMENTED YET
      #        - provider: ldap_ad
      #          type: group
      #          value: "admin_staff"

      permissions:
        - resource: applicationconfig
          actions: all

        - resource: clusterconfig
          actions: all

        - resource: topic
          value: ".*"
          actions: all

        - resource: consumer
          value: ".*"
          actions: all

        - resource: schema
          value: ".*"
          actions: all

        - resource: connect
          value: ".*"
          actions: all

        - resource: ksql
          actions: all

        - resource: acl
          actions: all

        - resource: audit
          actions: all

Steps to reproduce

Use the startup script and configuration file provided in the above steps (need to be modified to the correct Kafka cluster address) to deploy using java -jar. Finally, observe whether the Kafka cluster exists on the Kafka-ui console page.

Screenshots

Logs

tandard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts

---

| | | |_ | / |_ _ _ /\ _ __ __ _ | | ___ | |/ /_ _ / | |____
| || || | | / _ | '| / _ | '_ / / _| ' \/ -_) | ' </ _ | | / / `|
_/|| || ___|| // _| .___,_|||___| ||__,|| |__,|
|_|

2025-07-24 11:57:39,656 INFO [background-preinit] o.h.v.i.u.Version: HV000001: Hibernate Validator 8.0.1.Final
2025-07-24 11:57:39,775 WARN [main] c.p.k.u.u.DynamicConfigOperations: Dynamic config file /etc/kafkaui/dynamic_config.yaml doesnt exist or not readable
2025-07-24 11:57:39,781 INFO [main] c.p.k.u.KafkaUiApplication: Starting KafkaUiApplication using Java 17.0.15 with PID 3467253 (/usr/local/develop/big-data/kafka-ui/kafka-ui-api-v0.7.2.jar started by root in /usr/local/develop/big-data/kafka-ui)
2025-07-24 11:57:39,782 DEBUG [main] c.p.k.u.KafkaUiApplication: Running with Spring Boot v3.1.3, Spring v6.0.11
2025-07-24 11:57:39,783 INFO [main] c.p.k.u.KafkaUiApplication: The following 1 profile is active: "local"
2025-07-24 11:57:44,499 DEBUG [main] c.p.k.u.s.SerdesInitializer: Configuring serdes for cluster local
2025-07-24 11:57:45,490 INFO [main] o.s.b.a.s.r.ReactiveUserDetailsServiceAutoConfiguration:

Using generated security password: 516fed9d-6cb6-4b9b-865e-724dbcf2ace5

2025-07-24 11:57:45,683 WARN [main] c.p.k.u.c.a.DisabledAuthSecurityConfig: Authentication is disabled. Access will be unrestricted.
2025-07-24 11:57:46,033 INFO [main] o.s.b.a.e.w.EndpointLinksResolver: Exposing 1 endpoint(s) beneath base path '/actuator'
2025-07-24 11:57:46,889 INFO [main] o.s.b.w.e.n.NettyWebServer: Netty started on port 18888
2025-07-24 11:57:46,939 INFO [main] c.p.k.u.KafkaUiApplication: Started KafkaUiApplication in 8.312 sec

-07-24 13:36:47,095 DEBUG [boundedElastic-1] c.p.k.u.s.m.JmxMetricsRetriever: 575 metrics collected for service:jmx:rmi:///jndi/rmi://xxx:9997/jmxrmi
2025-07-24 13:36:47,096 DEBUG [boundedElastic-1] c.p.k.u.s.ClustersStatisticsScheduler: Metrics updated for cluster: local
2025-07-24 13:37:16,935 DEBUG [parallel-1] c.p.k.u.s.ClustersStatisticsScheduler: Start getting metrics for kafkaCluster: local
2025-07-24 13:37:16,938 DEBUG [boundedElastic-1] c.p.k.u.s.m.JmxMetricsRetriever: Collection JMX metrics for service:jmx:rmi:///jndi/rmi://xxx:9997/jmxrmi
2025-07-24 13:37:17,060 DEBUG [boundedElastic-1] c.p.k.u.s.m.JmxMetricsRetriever: 575 metrics collected for service:jmx:rmi:///jndi/rmi://xxx:9997/jmxrmi
2025-07-24 13:37:17,060 DEBUG [boundedElastic-1] c.p.k.u.s.ClustersStatisticsScheduler: Metrics updated for cluster: local
2025-07-24 13:37:46,934 DEBUG [parallel-7] c.p.k.u.s.ClustersStatisticsScheduler: Start getting metrics for kafkaCluster: local
2025-07-24 13:37:46,936 DEBUG [boundedElastic-1] c.p.k.u.s.m.JmxMetricsRetriever: Collection JMX metrics for service:jmx:rmi:///jndi/rmi://xxx:9997/jmxrmi
2025-07-24 13:37:47,052 DEBUG [boundedElastic-1] c.p.k.u.s.m.JmxMetricsRetriever: 575 metrics collected for service:jmx:rmi:///jndi/rmi://xxx:9997/jmxrmi
2025-07-24 13:37:47,052 DEBUG [boundedElastic-1] c.p.k.u.s.ClustersStatisticsScheduler: Metrics updated for cluster: local

Additional context

What is strange is that I use docker to deploy kafka-ui using the same cluster configuration as before. This can indeed be loaded into the kafka cluster. Why is this?

[Haarolean]

this repo is no longer maintained (#4255), please refer to: https://github.com/kafbat/kafka-ui
regarding your issue: you have RBAC enabled and auth disabled. There's no way you can get permissions assigned without authentication method, and there's a clear message about this in logs.

[kiwar199]

Broker Count-show list wrong