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
A server may care about which user has connected. I'm not seeing a path to connect the SSH user name to any of my handler code. I'm not even seeing it saved and available in SSHChildChannel or anything hanging off of it.
Unless I've missed something this will take some doing to add. Options include:
Adding a SSHChannelRequestEvent with a description of the user name which is sent first.
NIOSSHHandler() could get a new initializer which passes authentication information into the inboundChildChannelInitializer: equivalent.
Either of these presuppose that the user name is saved somewhere.
The text was updated successfully, but these errors were encountered:
Right now we avoid putting a structure on how the user authentication credentials are passed. This is managed entirely by the user authentication delegate, and we persist no state to that effect.
However, I think it’s a good idea to persist the logged in username, yeah. The proper API design is likely to store the auth information on the NIOSSHHandler, and then expose it to child channels via a new channel option. Users can get that channel option to request the information, which we’ll then load from the NIOSSHHandler.
A server may care about which user has connected. I'm not seeing a path to connect the SSH user name to any of my handler code. I'm not even seeing it saved and available in
SSHChildChannel
or anything hanging off of it.Unless I've missed something this will take some doing to add. Options include:
Adding a
SSHChannelRequestEvent
with a description of the user name which is sent first.NIOSSHHandler()
could get a new initializer which passes authentication information into theinboundChildChannelInitializer:
equivalent.Either of these presuppose that the user name is saved somewhere.
The text was updated successfully, but these errors were encountered: