Configuration for IoT devices

Open
#1,665 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
authentication, authorization, embedded-iot, security

Research direction

The issue names no files, tests, or entry points; begin by locating the MQTT broker's certificate authentication and topic authorization configuration. Done means documenting or providing a way for certificate-identified devices to connect and restrict read/write access to their own namespaced topic.

Written by the indexing model from the issue text.

Description

My IoT devices are pre-loaded with certificates, and each one has a private key, and my server has the corresponding public key

how do I use that to only allow my devices to connect to the MQTT broker, and also to only allow devices to publish on their "namespaced" channel, eg if the "Name" in the certificate is "device-xyz", it can only read/write on /devices/device-xyz or similar?

Dominant language
Java
Stars
190
Forks
56
Avg merge
27m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from streamnative/mop

All issues in streamnative/mop

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.