You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently the browser based terminal needs to be used to log in using ssh.
This way you cannot use your preferred terminal emulator to log in
Describe the solution you'd like
It would be really nice if the RAC Outpost had an ssh port open.
selecting different applications could be done like ssh <application>@authentik.example.com.
This has the issue of authentication.
I've seen projects like Teleport return an url to authenticate the session when trying to connect. Once the user has logged in, the ssh session gets forwarded to the server.
Alternatively a "simpler" solution might be allowing users to add ssh public keys to their account, when trying to connect we can validate the user's access using his key he's connecting with
The text was updated successfully, but these errors were encountered:
the outpost won't have an SSH port but we are exploring different options for allowing CLI-based SSH access without needing a browser
Awesome! I'm glad to hear it, i'll be curious to find out what you'll come up with.
I'm not married to the idea of it needing to be an ssh port, but i do love my own terminal emulator 🙂
Is your feature request related to a problem? Please describe.
Currently the browser based terminal needs to be used to log in using ssh.
This way you cannot use your preferred terminal emulator to log in
Describe the solution you'd like
It would be really nice if the RAC Outpost had an ssh port open.
selecting different applications could be done like
ssh <application>@authentik.example.com
.This has the issue of authentication.
I've seen projects like Teleport return an url to authenticate the session when trying to connect. Once the user has logged in, the ssh session gets forwarded to the server.
Alternatively a "simpler" solution might be allowing users to add ssh public keys to their account, when trying to connect we can validate the user's access using his key he's connecting with
The text was updated successfully, but these errors were encountered: