Skip to content

docs: clarify MQTT password-based authentication credentials#1285

Draft
jainrocks wants to merge 6 commits intomasterfrom
docs-mqtt-auth-1912876625227867514
Draft

docs: clarify MQTT password-based authentication credentials#1285
jainrocks wants to merge 6 commits intomasterfrom
docs-mqtt-auth-1912876625227867514

Conversation

@jainrocks
Copy link
Copy Markdown
Collaborator

This PR clarifies the credential requirements for MQTT password-based authentication in the client documentation, explicitly stating the password derivation from the private key and the username formatting.


PR created automatically by Jules for task 1912876625227867514 started by @jainrocks

Documents the formatting of the username (`/r/<registry_id>/d/<device_id>`)
and the derivation of the password (the first 8 characters of the sha256sum
of the private pkcs8 file) for password-based MQTT authentication.

Co-authored-by: jainrocks <6883641+jainrocks@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@jainrocks jainrocks marked this pull request as draft April 8, 2026 15:00
google-labs-jules bot and others added 4 commits April 8, 2026 17:31
Documents the formatting of the username (`/r/<registry_id>/d/<device_id>`)
and the derivation of the password (the first 8 characters of the sha256sum
of the private pkcs8 file) for password-based MQTT authentication.

Co-authored-by: jainrocks <6883641+jainrocks@users.noreply.github.com>
Documents the formatting of the username (`/r/<registry_id>/d/<device_id>`)
and the derivation of the password (the first 8 characters of the sha256sum
of the private pkcs8 file) for password-based MQTT authentication.

Also adds pkcs to .wordlist.txt to fix the CI spellchecker failure.

Co-authored-by: jainrocks <6883641+jainrocks@users.noreply.github.com>
Documents the formatting of the username (`/r/<registry_id>/d/<device_id>`)
and the derivation of the password (the first 8 characters of the sha256 hash
of the private pkcs8 file) for password-based MQTT authentication.

Also adds pkcs to .wordlist.txt to fix the CI spellchecker failure.

Co-authored-by: jainrocks <6883641+jainrocks@users.noreply.github.com>
Documents the formatting of the username (`/r/<registry_id>/d/<device_id>`)
and the derivation of the password (the first 8 characters of the sha256 hash
of the private pkcs8 file) for password-based MQTT authentication.

Also adds pkcs and sha256 to .wordlist.txt to fix the CI spellchecker failure.

Co-authored-by: jainrocks <6883641+jainrocks@users.noreply.github.com>
@noursaidi
Copy link
Copy Markdown
Collaborator

I don't think we should document this because it's not ideal behavior.

Typically when client certificates are used (as they are in the current configuration) passwords would not be used, and I believe that mosquitto doesn't validate passwords when client certificates are provided

Documents the formatting of the username (`/r/<registry_id>/d/<device_id>`)
and explicitly states that password-based authentication is not used when
client certificates are configured, which is typical.

Also adds Mosquitto to .wordlist.txt to pass spellchecks.

Co-authored-by: jainrocks <6883641+jainrocks@users.noreply.github.com>
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

Successfully merging this pull request may close these issues.

2 participants