MQTT, x.509 certificate-based authentication: use the correct key name for the TLS SAN type configuration parameter (backport #12604) #12618
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
It fixes an issue caused when the
mqtt.ssl_cert_client_id_san_type
was renamed in the schema to 'mqtt.ssl_cert_login_san_type` to keep it consistent with how the username is determined. But one part of the code was not updated accordingly.Adding a selenium end-2-end test so that this kind of issues are spotted earlier.
References #12595.
Types of Changes
What types of changes does your code introduce to this project?
Put an
x
in the boxes that applyThis is an automatic backport of pull request #12604 done by [Mergify](https://mergify.com).