How to participate in the authentication information for websocket connection custom authentication
Open
lifecycle/stale
type/bug
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
Pulsar turns on custom authentication. When my custom authentication gets the parameters, it will query the database. How to pass the authentication parameters using the websocket connection, and how does the server get the parameters
Contributor guide
Research direction
The issue mentions Pulsar custom authentication and WebSocket connections but names no file, test, or entry point. Start by tracing the WebSocket authentication flow and its parameter handling, then document how clients pass authentication parameters and how the server receives them; done means a clear, tested usage explanation.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authentication
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100