Enable TLS for trajectory server

Open
#16 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
backend, security

Research direction

Start by locating the TrajectoryServer entry point in rmf_visualization_scheule and reading the existing JWT token verification path. Determine how its websocket traffic is exposed and what rmf-web requires for wss/https support. Done means TrajectoryServer can serve encrypted traffic without exposing JWT tokens or payloads.

Written by the indexing model from the issue text.

Description

enhancement

Feature request

Add TLS support for TrajectoryServer in rmf_visualization_scheule.

Description

Rmf-web requires that websocket messages sent over be encrypted. Right now, we have a jwt token verification process implemented but not yet for TLS (wss/https) support. TLS is required so that hackers will not be able to gain access to the jwt token or payload when sending data over.

Dominant language
C++
Stars
32
Forks
23
Avg merge
37m
Merged PRs (30d)
1

Getting set up

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 open-rmf/rmf_visualization

All issues in open-rmf/rmf_visualization

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.