-
Notifications
You must be signed in to change notification settings - Fork 18
Open
Labels
needs triageTeam needs to triage this issueTeam needs to triage this issue
Description
Code of Conduct
- I agree to follow this project's Code of Conduct
On what operating system are you seeing the problem?
macOS (Apple/arm64)
VS Code version
Version: 1.110.0-insider
Commit: 404102fc70f6f15e1aba226b6d56f4c75bd5fa4e
Date: 2026-02-26T17:40:44.245Z
Electron: 39.6.1
ElectronBuildId: 13369494
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0
Version of Confluent extension
2.2.0
To Reproduce
Create a new connection and enter username longer than 96 characters.
Current vs. Expected behavior
Expected to be able to create a new connection.
Relevant log output
x Failed to test connection. {"status":"400","code":"invalid_input","title":"Invalid input","id":"705e985b-db7a-4b60-b742-5e1804d66142","errors":[{"detail":"Kafka cluster username may not be longer than 96 characters","source":"kafka_cluster.credentials.username"}]}Which area(s) are affected? (Select all that apply)
Connections
Additional context
Issue happens all the time.
The username is long because the Oracle Cloud Streaming appends a pool id to the user name.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
needs triageTeam needs to triage this issueTeam needs to triage this issue