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

[Feature] Reverse agent connection #281

Open
AndreKR opened this issue Jan 29, 2025 · 1 comment
Open

[Feature] Reverse agent connection #281

AndreKR opened this issue Jan 29, 2025 · 1 comment

Comments

@AndreKR
Copy link

AndreKR commented Jan 29, 2025

Currently the periphery agent needs to be reachable and have valid TLS certificates so that the server can connect to the agent.

If the agent could connect to the server instead, Komodo would be able to manage devices that do not provide a web server (or any server at all).

It would also simplify certificate management because only the server would need to have valid TLS certificates, not every agent.

This is related to #123 and #147.

@mbecker20
Copy link
Member

Yes I have considered this and agree, I was planning this for Komodo v2 (it would definitely be breaking change for existing users). The idea is the Periphery agent is given a Core endpoint and an identity token generated by Core unique to each server. Then they will persist outbound websocket connection to Core to achieve duplex communication.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants