jenkinsci / jenkinsci/active-directory-plugin
[JENKINS-10341] Active Directory plugin produces excessive Logon Audit records in domain controller
- Dominant language
- Java
- Stars
- 53
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Description
I just got a visit from one of our IT guys who noticed that we're getting a large volume of Logon Audit records in the event log of our domain controller that are all coming from our Jenkins install. In particular, several of our developers are using the "Hudson Tray Tracker" tool to monitor status of our jobs, and it appears that every refresh causes multiple logon events to fire. We're seeing 10+ events per second per user, which seems excessive.
Some of the blame may lie with the tray tracker app, but even if it's checking every second, that's still an impressive number of Logon events to be firing. Our IT guys tell me it's overwhelming their logs and they're having trouble dealing with it. Is there anything Jenkins can do to reduce this problem?
---
Originally reported by
dpryden, imported from: Active Directory plugin produces excessive Logon Audit records in domain controller
Raw content of original issue
I just got a visit from one of our IT guys who noticed that we're getting a large volume of Logon Audit records in the event log of our domain controller that are all coming from our Jenkins install. In particular, several of our developers are using the "Hudson Tray Tracker" tool to monitor status of our jobs, and it appears that every refresh causes multiple logon events to fire. We're seeing 10+ events per second per user, which seems excessive.
Some of the blame may lie with the tray tracker app, but even if it's checking every second, that's still an impressive number of Logon events to be firing. Our IT guys tell me it's overwhelming their logs and they're having trouble dealing with it. Is there anything Jenkins can do to reduce this problem?
- environment:
Windows Server 2003 R2 64-bit; Jenkins 1.419; Active Directory plugin 1.18
Contributor guide
Research direction
Start with the active-directory-plugin authentication path and reproduce the repeated requests using Hudson Tray Tracker against the stated Jenkins 1.419 and Active Directory plugin 1.18 environment. Done means reducing unnecessary domain-controller Logon Audit records while preserving authentication; the issue names no source file or test, so locate those before changing anything.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100