Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Support custom http headers for websocket connections #1722

Open
msalajka opened this issue Jul 16, 2024 · 1 comment
Open

[Feature] Support custom http headers for websocket connections #1722

msalajka opened this issue Jul 16, 2024 · 1 comment
Assignees
Labels
CLI MQTTX CLI desktop MQTTX Desktop discussion This issues and pr are worth discussing feature This pr is a feature web MQTTX Web
Milestone

Comments

@msalajka
Copy link

Motivation

Authentication: Custom headers can include authentication tokens (e.g., JWTs, API keys) that are necessary to authenticate users or devices before establishing a connection.

Custom Protocols: In some use cases, clients and servers might follow proprietary or custom protocols that require specific headers to establish a connection or negotiate terms (for example vmware cloud director requires to set header Sec-WebSocket-Protocol to mqtt to establish a WebSocket connection).

@msalajka msalajka added the feature This pr is a feature label Jul 16, 2024
@ysfscream ysfscream self-assigned this Jul 17, 2024
@ysfscream ysfscream added discussion This issues and pr are worth discussing CLI MQTTX CLI web MQTTX Web desktop MQTTX Desktop labels Jul 17, 2024
@ysfscream ysfscream modified the milestones: v2.0.0-alpha.1, v1.11.0 Jul 18, 2024
@ysfscream
Copy link
Member

This is a good suggestion. We will consider whether we can support it. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLI MQTTX CLI desktop MQTTX Desktop discussion This issues and pr are worth discussing feature This pr is a feature web MQTTX Web
Projects
Status: In Progress
Development

No branches or pull requests

2 participants