- changed status to resolved
Reconnect with different username
Issue #1
resolved
Reconnecting to the same host with a different username doesn't user the new username since the information is found in the outbound_session_map.
Scenario:
- Connection with user "foo" to a host.
- Don't close the original connection, connection with user "bar"
Now, it's not clear what the behavior should be. Options:
- Throw an exception on the second connection attempt saying we're already connected with different credentials.
- Disconnect the original connection and attempt to reconnect with the new credentials.
Comments (1)
-
reporter - Log in to comment
This was fixed quite a while ago with session reconnection tokens... stale bug