[BUG] ssh monitor with proxyjump, triggering "Too many authentication failures" exception
- Dominant language
- Java
- Stars
- 7.4k
- Forks
- 1.3k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 32
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Current Behavior
The global singleton sshClient was shared across all connections, causing identity (passwords/keys) to accumulate globally. When with ProxyJump - authentication attempts would mix identities from different sessions, exceeding the server's MaxAuthTries and triggering "Too many authentication failures".
### Expected Behavior
_No response_
### Steps To Reproduce
_No response_
### Environment
```markdown
HertzBeat version(s): 1.7+
```
### Debug logs
_No response_
### Anything else?
#3926
_No response_
Contributor guide
Research direction
Start by locating the SSH monitor connection setup and the global singleton sshClient described in the issue, then trace how ProxyJump sessions collect identities. Reproduce the authentication-failure case if possible; done means separate sessions no longer mix credentials or trigger the server's "Too many authentication failures" error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100