-
-
Notifications
You must be signed in to change notification settings - Fork 142
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(agent,pkg): remove timed authentication #4022
Conversation
434d164
to
24b3645
Compare
24b3645
to
4de5ccb
Compare
4de5ccb
to
7270bfc
Compare
7270bfc
to
a40fb05
Compare
a40fb05
to
93d0c9f
Compare
93d0c9f
to
6ef1258
Compare
6ef1258
to
9713079
Compare
To replace the re-authentication process that could be required if the server changed its API or SSH keys, we've added an a new error check on the dial process, that verify whether a `401` error is returned when the reverse tunnel is initialized to the server.
e29fe6a
to
652f881
Compare
652f881
to
bffd81c
Compare
c739e48
to
fe513d7
Compare
Authentication request is critical for the device presence on ShellHub, what makes its remotion difficult to do. One of the main limitations is the addition of devices to a namespace. When it is initialized, it authenticates on the namespace, and starts to listen for connections. If the device, after being accepted, is removed, the Agent won't notice it until it loses the connection to the server, showing it as offline in the system. To remove timed authentication, we should also be able to identify this deletion on the tunnel, or refactor core components for device to server communication, possibly breaking compatibility. JWT invalidation is also a problem, as the connection could also remain open while the tunnel is established. |
No description provided.