-
Notifications
You must be signed in to change notification settings - Fork 49
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
Is the SSH user name accessible by the ChannelHandler? #57
Comments
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 Is this a patch you’re interested in making? |
I write one up. |
+1 would love to see this feature added to the framework |
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: