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 Request] #56

Open
DavidHill0809 opened this issue Jul 27, 2023 · 1 comment
Open

[Feature Request] #56

DavidHill0809 opened this issue Jul 27, 2023 · 1 comment
Assignees

Comments

@DavidHill0809
Copy link

Is your feature request related to a problem? Please describe.
No, it is just an optimisation to reduce number of devices.

Describe the solution you'd like
Mixed authentication between X.509 certificate and Basic authentication.

We have TBMQ listening on a public IP address on port 8883 for X.509 authentication only and port 1883 on an Internal subnet and also on a VPN IP subnet. We would like to configure a single device that will allow X.509 authentication using the certificate CN on port 8883 or authenticate the same client_id (as the certificate CN) on port 1883 if it comes in through the VPN address or internal address. Without this we will need to set up 2 devices for each physical device.

Describe alternatives you've considered
TBMQ already does combination of authentication based on client_id, username, password, etc, but when you configure a device as X.509 certificate based the configuration there is no facility to also enable Basic authentication.

Additional context

@dmytro-landiak
Copy link
Contributor

Thank you for the request, we will consider it and will get back here once we have more updates for you regarding this topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants