-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
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)
In Kafbat UI, the Schema Registry "Global Compatibility Level" button is greyed out and cannot be enabled when RBAC is turned on in the configuration.
With RBAC disabled, the button works normally.
Using backend curl commands, the update works even with RBAC enabled.
The issue appears only in the UI layer under RBAC.
Expected behavior
The Global Compatibility Level button should be enabled when the logged-in user has the appropriate RBAC permissions.
Behavior should match the case when RBAC is disabled.
Your installation details
cd /opt
git clone https://github.com/kafbat/kafka-ui.git
cd kafka-ui
./mvnw clean package -DskipTests
kafka-ui-api/target/kafka-ui-api-.jar
cd kafka-ui-react-app
npm install
npm run build
kafka:
clusters:
- name: local
bootstrapServers: "localhost:9092"
zookeeper: "localhost:2181"
schemaRegistry: "http://localhost:8081"
ksqldbServer: "http://localhost:8088"
connect:
- name: local-connect
address: "http://localhost:8083"
spring:
security:
basic:
enabled: false
java -jar kafka-ui-api/target/kafka-ui-api-*.jar --spring.config.location=file:/opt/kafka-ui/config/application.yml
Steps to reproduce
Deploy Kafbat UI with RBAC enabled in the configuration.
Navigate to Schema Registry → Global Compatibility Level in the UI.
Observe that the button is disabled (greyed out).
Screenshots
No response
Logs
No response
Additional context
Issue only occurs in the UI layer under RBAC.
With RBAC disabled, the functionality works as expected.
Backend API calls are functioning correctly regardless of RBAC status.