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

Secure message exchanges for user equipment #138

Closed
2 of 3 tasks
tigroo opened this issue Jul 4, 2024 · 1 comment · Fixed by #173
Closed
2 of 3 tasks

Secure message exchanges for user equipment #138

tigroo opened this issue Jul 4, 2024 · 1 comment · Fixed by #173
Assignees
Labels
Python Python code
Milestone

Comments

@tigroo
Copy link
Collaborator

tigroo commented Jul 4, 2024

  • Use certificate to secure connection to the broker
    • MQTTS
    • WSS

GIVEN the public root CA that signed the certificate of the message broker was provisioned
AND the message broker hostname's was discovered
AND the message broker was configured to only accept secure connections
WHEN I establish a connection using the certificate
THEN the connection will succeed
AND I will be able to subscribe and publish

@tigroo tigroo added this to its-client Jul 4, 2024
@tigroo tigroo converted this from a draft issue Jul 4, 2024
@tigroo tigroo added the Python Python code label Jul 4, 2024
@tigroo tigroo added this to the Sprint 2 milestone Jul 4, 2024
@tigroo tigroo changed the title Secure message exchanges for User Equipment Secure message exchanges for user equipment Jul 4, 2024
@nbuffon nbuffon moved this from Open to Ready in its-client Jul 12, 2024
@nbuffon nbuffon modified the milestones: Sprint 2, Sprint 3 Sep 30, 2024
@nbuffon nbuffon added this to the Sprint 3 milestone Oct 8, 2024
@ymorin-orange
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Python Python code
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants